Every app that you can create in Celoxis has the following componentselements:
States: States represent "Stages" in your app. Each state is a logical check point in the process where a specific activity is expected to be performed. Every state has a Start start and end state.
For instance, in an "Order Fulfillment App", for an issue the following states may exist: "Order ReceivedUnresolved", "Payment AuthorizedOn Hold", and "Goods ShippedResolved", "Payment Capturedwhile for a risk the states are "Not Occurred", "Closed". Other states might be "Payment Not AuthorizedOccurred", "Order RejectedDeferred" and "Order Canceled By CustomerMitigated".
Workflow: These are the actions you can perform in an app. For instance, a bug in the state "FixedBug" can be transitioned to "Re-open" because the bug fails a test or it may go to "Closed" because its fixedfrom "In Verification" to "Bug Confirmed" once it is verified by a member of the QA team.
Requestor: The initiator for an app. E.g. in a leave approval an issue app, the requestor will be the person who is applying for the leave.can be a customer or another employee. You can define templates for emails sent to a requestor of an app item
Triggers: Celoxis provides a way to perform actions based on email triggers from the requestor.
State Managers: State managers are users who are responsible when an app is in a particular state. They receive notifications (if enabled) for delayed items, etc.
Timeout Policies: Timeout policies help you define rules on what should happen if an app remains in a state for a given time. For example, In a bug tracking app, if the bug remains in the "OpenIn Verification" state for 24 hours then it may be required to notify the state manager.
Security: With each custom app, you can define roles, assign permissions and specify users who can play those roles.