Tips and Tricks

Enhance your experience with Blueprint AI by following these best practices. Stay organized and ensure consistency across environments with these helpful tips!

​​

Foundation Data

​

• Ensure Foundation Data is Synchronized: Keep foundational data aligned across environments to prevent mismatches. For example, if a flow references an assignment group that exists in Production but not in Development, the group value may be incorrect or missing, leading to issues in flow execution.

 

New Blueprint - Service Catalog

​​

Form and Flow Requirements

​

• Define Groups Clearly in Flows: When designing flows, routing approvals, or assigning tasks, always specify "group" and provide an exact group name or the closest match to avoid confusion.

​​

• Specify Ticket Type: When outlining flow requirements, clearly indicate the type of ticket to be created (e.g., Incident, Task, Change) to ensure proper process execution.

​

• Avoid Flow Naming Conflicts: Many Blueprints may have similar requirements, so avoiding creating flows with the same name is essential. When AI builds a flow, it checks if the flow already exists. However, if two Blueprints are being developed simultaneously, AI may create a new flow with the same name for both. This can cause issues when a catalog item is submitted, as it may trigger the wrong flow. To prevent this, do not submit multiple Blueprints for development simultaneously. Instead, complete one Blueprint before starting another to ensure unique flow creation and avoid conflicts.

​

New Catalog Item

​

Image Based Requirements

​

• Use Clear Visual Indicators: Ensure mandatory fields, reference fields, and key elements are clearly marked.
  ​​

• Clarification on Icons: Avoid using extra icons such as the magnifying glass, upside-down triangle, or toggle switch. These can create confusion, making it unclear whether they represent mandatory fields or other functionalities.
  ​

• Submit One Image at a Time: Avoid including multiple images in a request
  ​

• Use High-Quality Images: Ensure the images are clear and adequately formatted before submission
  ​

• Check Image Orientation: Verify the correct orientation and rotation before submitting.
  ​

• Avoid Workflow Format for Form Questions: When documenting form questions, do not present them in a workflow diagram. Instead, structure them based on the form layout.

​​

New Blueprint - General

​

Tables, Dictionaries, and Forms

​​​

• Avoid Workflow Format for Form Questions: When documenting form questions, do not present them in a workflow diagram. Instead, structure them based on the form layout.
   

• Creating New Dictionaries: Clearly define the table where the new dictionary should be created.
   

• Updating Existing Dictionaries: Always reference the correct field and table.
   

• Adding Dictionaries to a Form: Always include the table name and the view (e.g., Default view) where the dictionary should be added on the Form. For example, “On the Change table, in the Default view, add a field ‘Long Description’ right after the Description field.”
   

• Removing Dictionaries from a Form: If the intent is to remove a field entirely from the form layout (not just hide it), use wording like “remove this field” instead of “remove visibility.” Phrases like “remove visibility” may cause AI to default to a UI Policy, which only hides the field visually.
   

• For Conditional Visibility, Separate Creation and Display Logic: When creating a new field that is conditionally shown (e.g., only when a specific value is selected), first define the field, including its placement, tab, and view. Then, describe the visibility rule separately, such as “only show this field when Close Code is ‘Successful with issues’ or ‘Unsuccessful’.”