Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Using localAction with replaceCurrent and modalDialog

Updated on October 12, 2022

You can use localAction in your applications using Dev Studio, but the Traditional Starter Packs do not currently support post-processing with the replaceCurrent and modalDialog actions. However, there are some behaviors using these actions that you can configure only using the Traditional Starter Packs. Both aspects are described in the following tables. 

Behavior when using modalDialog 

Behavior when using the modalDialog local action
BehaviorDescriptionPega PlatformDX Starter Packs
Post processing Executes post processing configured in the flow action on SubmitSupportedNot supported
Field limitLimits fields to those in the main flow actionNot supportedSupported
Value commitCommits values upon submitting the action Not supportedNot supported

Behavior when using replaceCurrent 

Behavior when using the replaceCurrent local action
BehaviorDescriptionPega PlatformDX Starter Packs
Post processing Executes post processing configured in the flow action on SubmitSupportedNot supported
Field limitLimits fields to those in the main flow actionNot supportedSupported
Value commitCommits values upon submitting the action SupportedNot supported
Cancel actionCancelling the action exits case processingSupported

Not supported

(returns to the main flow action)

Tip: For more information about how DX APIs handle actions, see Implementation of actions in DX API.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us