Tip: You can use filters for better results
-
Latest News
-
Quick Start
-
Work Place
-
-
-
- Manage Parts
- Assign Partners
- Interaction Buttons
- Workflow Buttons
- Ticket Info and COMS Buttons
- Schedule Tickets
- Edit Ticket Details
- Cancel Tickets
- Remove Tickets from the Ticket Clipboard
- Report Tickets
- Create Intervention Info
- Create Intervention Reports
- Cancel Appointments
- Clone Tickets
- Edit Privat Notes
- Inline Skill Editing
-
Admin Panel
-
- ServiceNow Connection
- Create Test Tickets
- Aliases Usage
- Workflows Usage
- What are Appearances in context of workflows?
- What are Buttons in context of workflows?
- What are Automations in context of workflows?
- What are Guides in context of workflows?
- What are Actions in context of workflows?
- Optimizer Settings
-
- Automations Section Explained
- Workflows Usage
- What are Actions in context of workflows?
- What are Guides in context of workflows?
- What are Automations in context of workflows?
- What are Buttons in context of workflows?
- What are Appearances in context of workflows?
- Workflow Monitoring
- Ticket Automated Actions
- Custom Object Automated Actions
- Conditions Settings
- Indications Settings
-
Fieldcode FMA app
-
Customer Portal
We are currently still laying the groundwork for Dynamics, so please treat this topic as a pre-read. If you need Dynamics configured right now, please reach out to the Support.
This specific feature set is only available for customers with a Business plan or an Enterprise plan.
What are Custom Object Automated Actions?
With custom automated object automated actions you can automatize processes for your customized created model. They basically work the same as ticket automated actions, with the only difference, being that they only apply to your custom models.
You can think of automated actions as a sandbox for creating automation inside the Work place. The most common use of automated actions is automatically sending relevant information and updates to your end users.
By smartly configuring automated actions, model users are not burdened with unnecessary work, resulting in less organizational effort and allowing model users to focus on more important work. Our solution engineers can help you configure custom object automated actions to fully meet and match your exact business requirements.
Inside the Admin panel go to Automations → Automated Actions
1. How to design Custom Object Automated Actions
- Decide if your action should be directly active in the system after creation. If you want your action to be directly active, switch the active switch to the right. If you are just preparing the action for now toggle the active switch to the left.
- Enter a name for your custom object automated action. Please avoid special characters and use underscores as connectors, otherwise you may run into the issue, that you cannot save your action.
- (Optional) - Enter a description for your new custom object automated actions. If you make your description clear and distinctive now, you will make it easier to distinguish between different actions.
- Select the object from the object dropdown. The action will only apply for this specific model.
You can select between three different action types:
- The Send email action sends out an email to a dedicated email audience. You can customize the email contents and use aliases by typing "@".
- The Create Info actions creates an ticket info. You can customize the ticket info contents and use aliases by typing "@".
- The Send SMS action sends out an email to a dedicated SMS audience. You can customize the email contents and use aliases by typing "@".
1.1 Send email action
This section is not finished yet, stay tuned!
1.2 Create info action
This section is not finished yet, stay tuned!
1.3 Send SMS action
This section is not finished yet, stay tuned!
2. How to test actions
This section is not finished yet, stay tuned!
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |