| Info |
|---|
CloudAware Applications support auto-attachment of objects enabled by the customer's workflow rulesprocesses that enable automatic attachment of objects to Cloudaware applications and improve asset management. |
| Table of Contents |
|---|
Description
Cloudaware application Application auto-attachment rules are based on Salesforce Workflow Rule functionality. A workflow rule is like an IF/THEN statement. IF part of the statement is called criteria, THEN part of the statement is called actions. For example, the simplest of workflows will check for a specific value on an object and then update the 'on Salesforce Flow functionality.
Flows are a powerful declarative tool used for process automation. Cloudaware application attachment flows update the Application Tier Client Name' field with a particular value. The value should be set to the application tier's name.
Note that 'Application Tier Client Name' consists of 2 parts: Application name and Application Tier name for example: AWS - Production (see the example below).
Create Application Attachment Workflow
1. field on an attachable resource (AWS EC2, RDS, Azure VM, etc.).
The value of the Application Tier Client Name then determines which Cloudaware Application and Application Tier a resource will be attached to. It uses the following format'<Cloudaware_Application_Name> - <Application_Tier'.
Prerequisites
Cloudaware Application(s) created with 1 or more Application Tiers (check the section 'Overview')
...
Creating an Auto-Attachment Flow
From your Cloudaware account open a main menu under your username.
2. Go to Setup → Workflow & Approvals → Workflow Rules Process Automation → Flows → New RuleFlow.
3. Choose the Record-Triggered Flow option for your new flow, and click Create.
...
4. Select the object to which this workflow rule applies. e.g. AWS EC2 Instance. Click Next.
...
4. Add Rule Name (1), set Evaluation Criteria(2) and Rule Criteria(3) to trigger your workflow rule. Add Filter Logic if necessary.
...
Click Save & Next.
4. Add Workflow Action → New Field Update.
...
5. Give this workflow acton a name. Select AWS EC2 Instance: Application Tier Client Name as a field to update.
...
6. Select a radio button Use a formula to set the new value. Enter the formula "Application Name" & " - " & "Application Tier Name". Click Save.
...
7. Review the workflow rule details. Click Done.
...
6. Click Activate to activate your workflow.
...
an Object you would like to set up an attachment rule for and set the trigger to 'A record is created or updated'.
...
5. Specify an entry condition. In this case, we will be creating attachment logic based on 'Application' and 'Environment' AWS tags values. Both fields should NOT be equal to an empty string.
...
6. Keep the 'Every time a record is updated and meets the condition requirements' option selected.
7. We are going to optimize the flow for Fast Field Updates. Click Done after setting this option.
...
8. Before specifying flow actions, we need to create a formula resource to get values from Application Tag and Environment Tag values. Open the ToolBox in the top left and click New Resource
...
9. Choose Formula resource type, specify the API name for it and choose ‘Text’ as the Data Type.
The formula should be formatted in the following way: {!$Record.<Application_Tag>} & " - " & {!$Record.<Environment_Tag>}.
...
10. Now we can configure the action that will be performing the actual Application Tier Client Name field update on a triggered object record. Choose Update Triggering Record in the shortcuts menu.
...
11. Set a label for the new element, and keep the 'Use the aws ec2 instance record that triggered the flow' option selected. In the Set Field Values for the Record specify the Application Tier Client Name as the field and ApplicationTierClientNameFormula as the value . Click Done.
...
12. After saving the flow the Activate button will become available. Click Activate.
Now the background process will be automatically matching the Application Client Tier Name values for triggered records with existing Cloudaware Applications and Application Tiers and perform the attachment.
Objects triggered by the flow and also their related objects (such as Network Interfaces and EBS Volumes for EC2) will be automatically attached to the appropriate application within 1 hour24 hours.
Attachment Logic Examples
...
Customers can create even more complicated auto-attachment rules combining workflow rules with formula fields configuring formula resources/fields inside flows or even updating update them via API from an external system. Almost any complex object classification logic is possible using workflows flows and formulas.
Object Re-Attachment After Application Tier Client Name Change
...