Transition effects on actions

You can include built-in transitions for actions that indicate that you have moved forward or backward in a case that uses flows in a custom mobile app. Transitions enhance the look-and-feel experience of the custom mobile app that you develop on Pega Platform. For example, you can use the transitions for back-to-back assignments in screen flows. The default is not to use transitions.

You can also specify a skeleton transition to enhance the look-and-feel experience of the custom mobile app. A skeleton transition displays a temporary animation in the form of an empty user interface structure while loading a screen in the app. You define a skeleton template with standard HTML tags and a CSS definition. Two default skeleton templates are available: pyOpenWorkSkeleton and pyLaunchHarnessSkeleton. You can also define additional custom skeleton templates.

The following actions support built-in transitions:

• Cancel (skeleton transition is not supported, by default)
• CreateWork
• GetNextWork
• OpenAssignment
• OpenWorkByHandle
• OpenWorkItem
• Save (Only when Close After Save is selected. Skeleton transition is not supported, by default)
• ShowHarness (skeleton transition only)