APIs & Integrations

yeti_t
Member

Remove option for merge fields on custom workflow action definition

We have a custom workflow action definition that includes a field called "Message name" which we allow the user to set so we can generate reports in our software. Typically this works just fine, but some users have used contact tokens inside the field, causing unique message names to come through to our system, generating reports for each unique message name.

Is there any option to disable contact tokens so they must enter a static value? Or if there is no option, is it possible to get an action identifier passed along? Currently, we receive `workflowId` but our user could have the same action type in the same workflow multiple times.

We appreciate the help!

yeti_t_0-1611679187268.png

 

0 Upvotes
2 Replies 2
himanshurauthan
Thought Leader | Elite Partner
Thought Leader | Elite Partner

Remove option for merge fields on custom workflow action definition

Hi @yeti_t

 

Have you tried making it "supportedValueTypes": ["STATIC_VALUE"] ?

 

"inputFields": [
{
"typeDefinition": {
"name": "widgetName",
"type": "string",
"fieldType": "text"
},
"supportedValueTypes": ["STATIC_VALUE"],
"isRequired": true
},

 

I hope this will solve your problem!

 

Best Regards,
@himanshurauthan 

Digital Marketing & Inbound Expert In Growth Hacking Technology
yeti_t
Member

Remove option for merge fields on custom workflow action definition

@himanshurauthan 
This is the current definition we have:

{
    "typeDefinition": {
        "name": "messageName",
        "type": "string",
        "fieldType": "text",
        "options": [],
        "optionsUrl": null,
        "referencedObjectType": null
    },
    "supportedValueTypes": [
        "STATIC_VALUE"
    ],
    "isRequired": true
}

 

0 Upvotes