Skip to end of banner
Go to start of banner

Predefined structure types

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Here is a list of predefined structures that are used throughout SIL™, usually with specific routines. Not enough for you? You can also define custom structures. Check our example in the Syntax section and roll your own.

Note that the structure fields can be modified, but the changes are not saved in the database. If you change a field for a project version variable, the project version will not be affected. Simply put, the structures are 'detached'.


NameFieldTypeNotes
idnumber
keystring
namestring
leadstringUser (lead)
contactstringAny contact for the customer set into the account
statusstringOne of: OPEN, CLOSED, ARCHIVED
customer_idnumber
customer_keystring
customer_namestring
category_idnumber
category_keystring
category_namestring
monthly_budgetnumber
globalboolean
billableboolean
idnumber
parentIdnumberAllocations are hierachical
scopeIdnumber
scopeTypestringlist of values: "account", "board", "project", "team", "folio", "none"
planItemIdnumber
planItemTypestringlist of values: "component", "epic", "issue", "project", "sprint", "version"
assigneestring
assigneeTypestringlist of values: "team", "user"
commitmentnumber
descriptionstring
workPerDaynumbernumber of hours
includeNonWorkingDaysboolean
startDatedate
endDatedate
createdBystringUser who created it
createddate
updatedBystring
updateddate
recurringboolean
recurrenceRulestringlist of values: "NEVER", "WEEKLY", "BI-WEEKLY", "MONTHLY"
recurrenceEndsdate
planApprovalIdnumber
planApprovalReviewerstring

id

number
namestring
missionstring
summarystring
leadstringUser (lead)
program_idnumber
program_namestring
program_managerstringUser, the Program Manager for the team
  • No labels