How can a Child Input (Import Forms Adj) be removed for a particular Workflow Profile?

How can a Child Input (Import Forms Adj) be removed for a particular Workflow Profile?

• A. It can be deleted
• B. The Profile Active is set to false for a given Scenario Type
• C. The Profile Active is set to false for the Default Scenario Type
• D. You cannot remove this

Answer: (B)

Controlling whether a Child Input is available in a workflow profile is done by the profile’s activation state for each Scenario Type. If you set the Profile Active flag to false for a specific Scenario Type, that input is not included in the workflow profile when that Scenario Type is chosen. This removes it for that scenario only, while leaving it active for other scenarios where the profile remains enabled. It’s a safe way to tailor which inputs appear in different planning contexts without deleting the input itself. For example, you can disable the input for a particular Forecast Scenario Type but keep it active for Actuals, so it won’t show up in that forecast workflow but remains usable in other contexts.

Controlling whether a Child Input is available in a workflow profile is done by the profile’s activation state for each Scenario Type. If you set the Profile Active flag to false for a specific Scenario Type, that input is not included in the workflow profile when that Scenario Type is chosen. This removes it for that scenario only, while leaving it active for other scenarios where the profile remains enabled. It’s a safe way to tailor which inputs appear in different planning contexts without deleting the input itself. For example, you can disable the input for a particular Forecast Scenario Type but keep it active for Actuals, so it won’t show up in that forecast workflow but remains usable in other contexts.