Why do Command arguments behave differently when using dictionary groups?
Why do Command arguments behave differently when using dictionary groups?
Understanding Command Argument Behavior with Dictionary Groups in Epsilon3
When constructing procedures in Epsilon3, you may encounter unique behaviors when using dictionary groups as the data source for commanding. This article explains how command arguments function in that context, the reasons for this behavior, and alternatives for certain use cases.
Why Command Arguments Do Not Appear at Edit Time
When using a dictionary group as the source for commanding within a procedure, you may notice that command arguments do not show up during the procedure editing phase. This behavior occurs because:
The specific dictionary from the group that will be used is only determined at runtime.
Each dictionary in the group may contain commands with different argument sets, preventing the application from displaying a fixed set of arguments at edit time.
This design allows flexibility to accommodate varying commands across dictionaries within the group but means argument information becomes available only after a dictionary is selected during procedure execution.
Presetting Command Arguments with Dictionary Groups
It is not possible to preset command arguments in Epsilon3 when using dictionary groups as the data source. This is because the arguments depend on which dictionary from the group is selected at runtime. If your workflow requires presetting all command arguments while editing a procedure, consider using a specific dictionary instead of a dictionary group. Single dictionaries provide a predictable and consistent set of arguments, making them better suited for scenarios where preset values are necessary.
Recommendations and Best Practices
Use dictionary groups when flexibility is essential, such as when commands may vary across different contexts or projects.
Opt for specific dictionaries when you need to define and preview command arguments before runtime.
Familiarize yourself with the commands and argument sets for each dictionary in your group to anticipate runtime behaviors and design procedures accordingly.
By understanding these limitations and choosing the appropriate data source for your needs, you can better utilize Epsilon3’s procedure capabilities efficiently.
How do I archive a procedure in Epsilon3?
How do I archive a procedure in Epsilon3?
Managing procedures effectively in Epsilon3 includes workflows like archiving older or unnecessary procedures. However, it is essential to understand the eligibility criteria and processes for archiving, particularly concerning draft and released statuses.
Can Drafts Be Archived?
No, drafts cannot be archived in Epsilon3. Draft procedures are designed for ongoing edits and can only be deleted, not archived. Archiving is exclusively available for procedures that have been released, meaning they have passed the draft stage and are formally finalized.
Step-by-Step Guide to Archiving a Procedure
To archive a procedure, follow these steps:
Open Epsilon3 and navigate to the procedure you want to archive.
Ensure the procedure is in a released status. Drafts cannot be archived.
Click on the three-dot menu located in the top-right corner of the procedure screen.
From the dropdown options, select Archive. Once archived, the procedure will no longer appear in the active list but can still be accessed in the archived procedures section if needed.
Key Points to Remember
Only released procedures can be archived.
Drafts can only be deleted if no longer needed.
Archival is reversible, ensuring flexibility in decision-making. With these steps and guidelines, you can effectively manage your procedures without confusion. For any additional support, consult the Epsilon3 support team.