Using an Order Guide to call another Order Guide in ServiceNow is generally not recommended and can lead to complications. Here are some reasons why this practice can be problematic:
Complexity and Maintenance:
- Nesting Order Guides can make the system more complex to manage and maintain. It can complicate troubleshooting and updating the guides.
User Experience:
- Users may become confused if one Order Guide calls another, making the user experience less intuitive and harder to follow.
Performance:
- Using multiple nested Order Guides can potentially affect system performance, especially if each guide contains numerous items.
Validation and Workflow:
- Managing validations and workflows can become more complex. Ensuring that validation rules and workflows are aligned across guides can be challenging.
Best Practices
It is generally better to use a single Order Guide and add all required catalog items within that guide. This approach allows you to:
- Maintain a simpler, more understandable structure.
- Ensure that all validations and workflows are centralized.
- Simplify system management and maintenance.
Alternatives
If you need to group items in different ways, consider the following solutions:
Catalog Categories:
- Use categories to organize catalog items, making them easily accessible without needing multiple guides.
Variables and Options:
- Use variables and options within a single Order Guide to offer users flexibility in their selections.
Subflows:
- Create subflows to handle specific parts of the ordering process instead of creating nested guides.
In summary, it is generally advisable to avoid calling one Order Guide from another. Keep your guides simple and centralize item management to improve maintainability and user experience.
