This article provides answers to frequently asked questions regarding Action Blueprints.
Frequently Asked Questions
Q: Who can create Blueprints? A: Only users with Admin permissions in Alpine have the capability to create, edit, copy, and delete Action Blueprints.
Q: Can I restrict Blueprints to specific Action types? A: Blueprints are designed to be versatile and are applicable to all Action types, rather than being limited to specific ones, ensuring ease of use and wide-ranging applicability.
Q: What happens when I edit an Action that was created with a Blueprint? A: When editing an Action that was originally created using a Blueprint, the system will display the standard Action modal rather than the Blueprint interface. The Blueprint is only used during initial Action creation, and any subsequent edits use the regular editing process.
Q: How does the data validation and search feature work in Action Blueprints? A: When creating an Action using a Blueprint, any part of the note section that includes a colon (e.g., Check Number: 1234) becomes searchable. This allows users to quickly find Actions by searching for keywords like “Check Number” and retrieving the associated values after the colon.
During Blueprint setup, fields intended for validation are marked with a : prefix. These designated fields are automatically extracted from the notes and used as validation fields when the Action is created. Once an Action is entered into Alpine, all validation fields are added back into the note section in a searchable format, ensuring they are both visible and easily retrievable via keyword search.
Q: If I edit or delete a Blueprint, will it affect actions that were already created with that Blueprint? A: No, editing or deleting a Blueprint will not affect any actions that were previously created using that Blueprint. Once an action is created, it exists independently of the Blueprint that was used to create it.
Q: Do I have to include campaigns in my Blueprint? A: Yes, every Blueprint must include at least one campaign requirement, either through category requirements or specific campaigns.
Q: Can I organize my Blueprints into folders? A: Folder organization systems are not included in this initial release but may be considered for future updates.
Q: What types of validation are supported for custom fields? A: Currently, the system supports Text, Number, and Date field validation. Additional validation types may be added in future releases.
Q: How does data validation work? A: When creating Action Blueprints, users can incorporate action fields, which can be numerical, date, or text-based. These fields can be designated as "required." If a user attempts to save an Action without completing a required field, an error will be flagged, prompting them to enter a value before proceeding. This mechanism, known as data validation, ensures greater consistency when inputting Actions into the database. Once an Action has been entered into Alpine, its corresponding action fields can be viewed within the "notes" section of that Action.
Related Articles
Create, Edit, Copy, and Delete Action Blueprints
How to Apply a Blueprint to a New Action
Action Blueprints Best Practices
If you have any questions or need assistance with setup and best practices, please reach out to your Customer Success Manager for support.