| Info |
|---|
Fact2field functionality allows users to define which Breeze facts Cloudaware must convert to fields on Force.com objects. Cloudaware will try to propagate fields containing caFact_ prefix with a matching Breeze fact. For example, if you create caFact_uptimehours field, Cloudaware will try to find uptime_hours fact and use its value. SUPPORTED FOR OBJECTS: AWS EC2 Instance Fact, AWS EKS Cluster Fact, Azure Virtual Machine Fact, Azure VM Scale Set Instance Fact, Azure AKS Cluster Fact, Google GCE Instance Fact, VCenter Virtual Machine Fact, CloudAware Physical Server Fact. |
Fact names use characters that are not in [a-zA-Z0-9], so you skip them in the field name: caFact_ansible_user_id will become caFact_ansibleuserid or caFact_ansibleUserId as A fact Name can be any but should start with caFact_ and be unique across Salesforce objects. The full fact name should also be provided in the Help Text area.
Example:
Name: caFact_userid or caFact_ansibleUserId (field names are not case-insensitive. )
Help Text: ansible.user_id
...
We recommend using any Text type for fact2field fields. Use a maximum length of 255 for Text/Text Area:
...
where CA10__CaAwsInstanceFact__c is API Name of the fact object, Name is the fact attribute that needs to be updated and %upgr% - its value that will be queried. This query will populate facts containing 'upgr' in their Name field on all AWS EC2 Instances.
Query examples:
| Code Block |
|---|
Update [SELECT Id FROM CA10__CaAwsInstanceFact__c WHERE Name = 'os.release.full']; |
...
| Code Block |
|---|
Update [SELECT Id FROM CA10_CaPhysicalServerFact__c WHERE Name like '%uptime%']; |
Start with using a query without filtering applied. However, if you face Apex CPU or limit exception errors, use the LIMIT/OFFSET clauses (see examples below):
| Code Block |
|---|
Update [SELECT Id FROM CA10__CaAwsInstanceFact__c WHERE Name = domain LIMIT 1000 OFFSET 0]; |
...