Skip to main content

Recipes Stages

About Recipe Stages​

Recipes follow a structured process to manage records effectively. This process is orchestrated through specific stages, ensuring each operation is executed smoothly and precisely. Let's delve deeper into these stages to understand their significance:

Create​

When a new record is being introduced to the crm, the Create operation ensures that the record is added accurately and efficiently:

  1. Validation​

    Before the record is even considered for addition, it undergoes a rigorous check using logic blocks. This validation ensures that all the data for the new record meets the defined criteria and requirements. Any discrepancies or issues are flagged at this stage, preventing the continuation of the process until they are resolved.

  2. Before Create​

    When the crm prepares to add a new record, a selected logic flow springs into action tailored to the particular use case. This initiation might encompass tasks like establishing default values, ensuring required dependencies are intact, conducting checks for potential duplicates, and performing necessary data transformations or mappings.

  3. After Create​

    Following the successful addition of the record, post-creation operations are executed using the designated logic flow. These operations might encompass activities like sending notifications about the new entry, activating workflows that hinge on this newly added data, or handling any other tasks needed once the data is in the crm.

Update​

Updating records is a delicate operation, and we ensure it's done with precision and care. Here's what happens during the update process:

  1. Validation​

    Before any changes are made, the system utilizes logic blocks to inspect the new data. These blocks examine the new information to ensure it meets established criteria and doesn't conflict with existing rules or standards. It's like a quick quality check before proceeding.

  2. Before Update​

    Before the actual update takes place, a logic flow you define springs to action. These flows might involve checking any relationships the record has with other data, ensuring no dependencies will be affected, and prepping the system for the changes. Think of it as ensuring everything is in order before the main event.

  3. After Update​

    Once the record is updated, post-update flows help finalize the process. These can range from updating any linked records that depend on the one just edited, launching tasks or workflows triggered by the change, or notifying relevant parties about the update. It's the system's way of tying up any loose ends.

Delete​

Removing a record from the system is a sensitive operation, and it's handled with utmost care:

  1. Validation​

    Before deletion, logic blocks scan the record to ensure that its removal won't disrupt the system or violate any dependencies.

  2. Before Delete​

    Before removing any record, the system uses flows to ensure there's no cascading impact. It checks for related records that might be affected, considers whether a data backup is necessary, and might even verify if all necessary approvals are in place.

  3. After Delete​

    Once the record is deleted, the system continues to operate with specific flows to manage subsequent tasks. These flows may include updating associated records, addressing leftover data points, or informing concerned parties about the removal of the record.