Talk:Configuring and extending stages, statuses, and work queues

1. Stages in PCS section mentions that more stages can be added by using the extensions provided. There is no further mention of how this is achieved. There is only a mention of "rename or remove any of the stages from the flow by using the Customize stage names decision rule" but nothing on adding new stages.
2. The image in "Extension for implementation teams" section has outdated usages such as "PRPC" and "work baskets". If these have been corrected in the product, the image must be updated.

The first level of organization of the tasks that are required to complete your business process. By providing stages, you organize work into logical phases that users of your application follow to reach an outcome. Stages visualize milestones or significant events in your business process and can also indicate a transition of work from one person to another. For example, if your business process is to review job applications, you can create Submission, Review, and Approval stages, each of which includes a different set of actions and is performed by a different person. Stages that are necessary to resolve a case through the basic, default path are called primary stages.

In a Microjourney™, stages are the milestones that leads towards an outcome.

The building blocks of your user interface, sections can use design templates for their structure and contain such interactive UI elements as fields, buttons, lists, and so on. A section creates a functional chunk of a user interface, and can be reused throughout your application for improved consistency and efficient development.

For example, your application may need to display user data as a list of ID cards. You can create a section for the contents of a card, and then reuse that section so that the design of every card is consistent.

The first level of organization of the tasks that are required to complete your business process. By providing stages, you organize work into logical phases that users of your application follow to reach an outcome. Stages visualize milestones or significant events in your business process and can also indicate a transition of work from one person to another. For example, if your business process is to review job applications, you can create Submission, Review, and Approval stages, each of which includes a different set of actions and is performed by a different person. Stages that are necessary to resolve a case through the basic, default path are called primary stages.

In a Microjourney™, stages are the milestones that leads towards an outcome.

The first level of organization of the tasks that are required to complete your business process. By providing stages, you organize work into logical phases that users of your application follow to reach an outcome. Stages visualize milestones or significant events in your business process and can also indicate a transition of work from one person to another. For example, if your business process is to review job applications, you can create Submission, Review, and Approval stages, each of which includes a different set of actions and is performed by a different person. Stages that are necessary to resolve a case through the basic, default path are called primary stages.

In a Microjourney™, stages are the milestones that leads towards an outcome.

The basic building blocks of an application, rules define the behavior of an application. There are many types of rules, each defining a different type of behavior. For example, rules define the display of a form, the fields that are used in your application, and the flows that define the process of completing work.

The system can reuse rules throughout your application. For example, in an application for ordering replacements parts, you can define a user interface to capture an address, and reuse the same rule for the UI to capture both the mailing address and the billing address for the order.

You define rules in an application to create a business solution for your organization and customers. Rules provide flexibility during the development process and help you design applications more efficiently, so that they can be implemented again in future projects.