General Structure of Template Processes

Reasons for single process for editing records.

We are delivering only one process for editing records and also for creating new records. (eg. opportunities, offers, tickets). Here are some reasons why this was not split up into 2 processes:

  • Only 1 process definition in the designer. If an additional phase should be created, you have to create the phase only for one process and for two.

  • We are opening only one process. It is not important if we are opening an existing opportunity or if we want to create a new one. The difference is the call of the process.

  • If a new record is created in a separate process, you have to switch to the “real” process after creating this record. By doing this, the whole header and all phases and metrics will be completely refreshed. This does not look very nice.

  • The process framework allows us to execute data providers with conditions. Therefore a data provider is not executed if the required records are not available. Therefore it is not necessary to split up a process into two parts.

Important:

In the offer process, a javascript is used to set the stage of the offer. This will NOT work if the offer is locked via the station right, because the JS code is running with the corresponding user rights. If you want to set the stage, although the offer is locked for editing, use a trigger or workflow.

Note: With the template we’re also delivering a configuration for the CRM.pad (“TE_ISI_TABLET” configuration).