New feature onboard: Simplify your app settings with App Configs

We are excited to announce a new feature that simplifies app configurations. Introducing App configs which enables you to conveniently store, access, and swiftly update all your configuration-related information.

What is App config?

App config is a JSON template that serves as a storage for all your configuration-related information. 

It allows you to effortlessly define a JSON structure consisting of key-value pairs to manage your app settings.

How to use App configs?

In Actioner, all workflows can seamlessly access configuration information from the app config. By using the notation config.{{configName}}.parameterKey, you can easily reference and retrieve values stored in the JSON config. 

This centralized approach allows you to control your app preferences, configuration values, and any other app settings from a single location. 

You can define multiple configs for a single app. When you need to make changes, simply navigate to the App config tab, locate the desired config, and update it effortlessly.

Example use case

Now, let's take a look at Conversational ticketing with Zendesk app. This app enables you to create triage channels, send hint messages to the ticketing channels, and configure CSAT preferences for your support team. 

To manage these preferences, you can store them in a JSON file. Here's an example of a supportTeamConfig JSON file:

{
 "appConfiguration": {
   "botIcon": "",
   "botName": "Actioner",
   "defaultTriage": "C0123456789",
   "triageThreadHint": "Conversation in this thread is synced with the ticket.<br> > Reply here to add public comments. If you start with :lock: emoji, your comment is added as a private note instead.<br>> :eyes: emoji assigns the ticket to you.<br>> :white_check_mark: emoji solves the ticket.",
   "requestThreadHint": "Nice work! Your ticket is created :raised_hands:<br>> :bulb: Conversation in this thread is synced with the ticket. Reply here to add a reply to your ticket.",
   "raiseRequestHint": "Are you looking to raise a request?",
   "dmThreadHint": "Nice work! Your request is created :raised_hands:<br>> :bulb: You can track your request's status here. You can also use :white_check_mark: **Solved** and :speech_balloon: **Reply** buttons to update your request.",
   "privateRepliesHint": "This request is now set as private :lock_with_ink_pen:<br>> :bulb: You can track your request's status here. You can also use :white_check_mark: **Solved** and :speech_balloon: **Reply** buttons to update your request."
 },
 "csatConfiguration": {
   "sendCsat": true,
   "csatTimeFrame": 1,
   "showScoreAsComment": true,
   "showScoreInTriage": true
 }
}

‍

Within any workflow, you can easily reference this information. When constructing your triage channel condition, you can use the expression config.supportTeamConfigs.defaultTriage to retrieve the channel ID value from the config file. 

If you need to change the triage channel later on, simply edit the JSON body without updating each individual workflow. This streamlined approach allows for efficient configuration management without the need for manual adjustments across multiple workflows.

Start Simplifying Your App Settings with App Configs

In summary, App configs revolutionize app settings management by providing a centralized, efficient, and easy-to-use solution. 

Experience the convenience firsthand by getting started with Actioner today. 

For ongoing support and interaction with our vibrant community, we invite you to join the Actioner Slack community. 

Your journey to hassle-free configuration starts here!

‍

‍