Parameters and their fields can be referenced via their names throughout Nimbus and also in external Systems using Nimbus Power Automate Connector. Nimbus users can expand this selection of system parameters by their own custom Parameters,  which allow “default” values to be set for later checks if Nimbus (or external Systems) have actually correctly written updates.

Parameter examples

From an system point of view, the parameters are storage placeholders for different purposes. In Nimbus there are two types of parameters to know:

💡Learning: Parameters can store anything and may be overwritten (if not hardcoded and read-only). They may be used to steer system behavior or contain custom context information.

Field examples

From a user point of view, the fields of a parameter can appear identical, e.g. an “Customer Address” field, but those fields can originate from different sources (CRM, Address book) via Flow Actions.

💡Learning: Fields can have identical names, but come from different parameters. A field refresh is done via Flow Actions at certain Trigger Events in your Workflows. 

Usage Examples

Using the Flow Actions in the Nimbus Power Automate Connector parameter fields and their values can be updated. This can be any static or dynamic value, e.g. retrieved from external systems. 

As previously mentioned, a mixture of system and custom fields are part of the JSON object as in a key/value pair. The customFields in this example are forming the bottom part of an Address Book which was previously created in the Nimbus configuration.

[
                                  {
                                    "addressBookId": "97ff7cf8-ee53-4de9-aca3-1287d2fea51e",
                                    "id": "eb30d621-a7cc-4fb3-b0f1-a046ed04e1df",
                                    "externalId": "03fac1cb-f00b-4521-b8c1-4c168752a7f5",
                                    "firstName": "Alessandro",
                                    "lastName": "Volta",
                                    "displayName": "Alessandro Giuseppe Antonio Anastasio Volta",
                                    "company": "Tenant Address Book",
                                    "jobTitle": "Scientist",
                                    "imAddresses": [],
                                    "emailAddresses": [],
                                    "businessPhones": [],
                                    "mobilePhones": [
                                      "123456789-10"
                                    ],
                                    "homePhones": [],
                                    "userPrincipalName": "avolta@lunifico.cloud",
                                    "addresses": [],
                                    "customFields": [
                                      {
                                        "name": "Achievements",
                                        "value": "Invented the battery"
                                      },
                                      {
                                        "name": "Birth Year",
                                        "value": "1745"
                                      },
                                      {
                                        "name": "Language",
                                        "value": "Italian"
                                      }
                                    ]
                                  }
                                ]

🔎 Address Books are just an example for storage for your parameter data. Here are some Power Automate Use Cases for your inspiration:

• Use Case - Storing External CRM Data in Custom Parameters 
• Use Case - Adding External Address Books via Power Automate 
• Use Case - Retrieving Azure AD Fields via Agent Token 
• Use Case - Looking Up a Caller to Open Dynamics 365 Contact Context
• Use Case - Creating a ServiceNow ticket based on user input
• Use Case - Looking up caller data from a simple Excel list
• Use Case - Working with Blacklists or Whitelists in Nimbus.