Business Process Flow

From Resco's Wiki
(Redirected from Process Flow)
Jump to navigation Jump to search
This article is about mirroring business process flows from Dynamics server in Resco mobile apps. For information about defining client process flows without any backend dependency, see Process.

The business process flow feature allows you to make certain business processes from Microsoft Dynamics CRM 2013 or later available in the Resco Mobile CRM app.

Configure in Woodford

  1. Select Process Flow from the Project menu of Woodford to enable business process flows in your app projects.
  2. Check the process flows that you want to enable.
  3. Click Validate Process to verify that the entity fields used by the process are enabled in your mobile projects; or click Validate All Processes to perform the check for all processes.
  4. If the check shows errors (a list of unavailable fields), click Enable Process Fields to enable them.
  5. When the Report column shows OK for all processes that you want to use, click Save.

Additional business logic

By default, business process flows are not compatible with client-side business logic in Resco mobile apps (i.e., rules or Resco JavaScript Bridge). For example, changes in the business process flow forms in the app do not trigger any On Change events. However, if you need to finetune your flows with client-side logic:

  1. Edit your app project in Woodford.
  2. Select Configuration from the Project menu.
  3. On the Dynamics tab, set Trigger events on Business Process Flow changes to true.
  4. Save all changes.

This setting allows you to use JSBridge to modify the flow behavior.

Conditional branching

TBD.

Use in the app

In the Resco Mobile CRM app, the business process flows are visualized as an additional tab, where it can be followed.

Localization

See how to localize the strings.

Offline mode

This limitation has been removed. Offline mode is supported.

We recommend using business process flows-related features in Resco apps in online mode. The offline mode restricts some functions. Most notably, you have to synchronize the app after each stage transition.

The way business process flows (BPF) are implemented in Dynamics CRM prevents applications from working with BPF in offline mode. It is because BPF can have multiple threads and if you go through more than one stage change before save and sync in offline, BPF does not know which path you went (even if the BPF is as simple as possible). Therefore, going through your steps one by one is basically the only way how you can use BPF in offline mode. If you progress through multiple stages while offline, you might encounter an error during synchronization: Invalid stage transition. Transition to stage {0} is not in the process active path.

See also