Hi, If I want to add [requested for ] field dynamically from the catalog item then how should I add that into decision table along with description? EX: Welcome [Requested for]
Hi there! Decision Tables are considered configuration or application data, just like flows and playbooks and can be moved between instances with the same processes as any other application data. They should follow the same deployment process that you use for any other app development. This can be Update Sets or Source Control and App Repo. -LH
You don't need to do anything special. (Create and) switch to the Update Set you want to track the Decision Table in. Make any changes and save. That's enough for it to be part of the current update set. If you are using the draft authoring feature and want the decision table to be available to be called from a flow, subflow or code snippet, you need to also publish the Decision Table. -LH
Hi, If I want to add [requested for ] field dynamically from the catalog item then how should I add that into decision table along with description?
EX: Welcome [Requested for]
Hi, I need to move the decision table to other environment like test env, what will be the best step to move the changes, except update sets?
Hi there! Decision Tables are considered configuration or application data, just like flows and playbooks and can be moved between instances with the same processes as any other application data. They should follow the same deployment process that you use for any other app development. This can be Update Sets or Source Control and App Repo.
-LH
Great demo, but how can a Decision Table be included in an Update Set?
You don't need to do anything special. (Create and) switch to the Update Set you want to track the Decision Table in. Make any changes and save. That's enough for it to be part of the current update set. If you are using the draft authoring feature and want the decision table to be available to be called from a flow, subflow or code snippet, you need to also publish the Decision Table.
-LH