Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Allow Velocity Script Tokens in Webhook PayloadDeclined

Currently, Webhook payloads do not allow Velocity Script tokens. Why not?Using a Velocity Script token to generate the JSON payload for a Webhook would be very helpful. For instance, the JSON structure of my Webhook could vary conditionally based on Lead and/or Program tokens. Currently, if I want to perform different actions in an external API, I would have to create numerous Webhooks. I don't want to have a different Webhook for each variation of my API calls. I would like to use a single Webhook, but vary the payload using the conditional logic of a Velocity Script.DesiredWebhook - Mail Item{     "leadId": {{lead.Id}},     "sku": {{my.SKU}},     "qty": 1,     "address": {          "name": {{lead.Full Name}},          "street": {{lead.Address}},          "city": {{lead.City}},          "state": {{lead.State}},          "postcode": {{lead.Postal Code}}     },     "data": {{my.Custom Script}}}Velocity Script Token - {{my.Custom Script}}{     "postcard_message": "Dear ${lead.FirstName},\\nYour subscription is about to expire on ${lead.subscriptionEndDate}.\\nRenew today!"}Velocity Script Token - {{my.Custom Script}} in another Program{     "brochure_image": "${my.brochureImage}",     "brochure_copy": "${my.brochureCopy}"}CurrentWebhook 1 - Mail Postcard{     "leadId": {{lead.Id}},     "sku": {{my.SKU}},     "qty": 1,     "address": {          "name": {{lead.Full Name}},          "street": {{lead.Address}},          "city": {{lead.City}},          "state": {{lead.State}},          "postcode": {{lead.Postal Code}}     },     "data": {          "postcard_message": {{my.Custom Postcard Message}}     }}Webhook 2 - Mail Brochure{     "leadId": {{lead.Id}},     "sku": {{my.SKU}},     "qty": 1,     "address": {          "name": {{lead.Full Name}},          "street": {{lead.Address}},          "city": {{lead.City}},          "state": {{lead.State}},          "postcode": {{lead.Postal Code}}     },     "data": {          "brochure_image_1": {{my.Custom Brochure Image}},          "brochure_copy": {my.Custom Brochure Copy}}     }}

ChristianBa2New Participant

Resource Planner: UI Improvements RequiredNew

We are using the resource planner to forecast our team onto planned/active projects. There is an activity internally to explore using this globally.Here are a few comments following our Snr. exec demo;The current UX is poor. Unable to see the full project name or resource role name.Entering values twice; once against the role/project and once against the specific user. It would be good to have an option to mirror the entry - speeds up the process.FTE is entered as a decimal; usually entered as a percentage. Lower priority.The product is slow to load.Adjust budgeting dates; the chevron on the left side is pointing in the wrong direction (it should be < instead of >).Adjust budgeting dates; should be renamed to something else, as it doesn't actually adjust anything, it just shows you if a particular period is low/high/overcapacity.Innovative idea 1; a lot of companies split forecasting by confirmed / unconfirmed projects. It would be valuable to assess building this option into the planner. Value: able to assess capacity load in the scenario your unconfirmed pipeline shifts to confirmed at the estimated start date. Are we able to manage the unconfirmed pipeline in that scenario. If not, I need to be ready to hire external consultants for example.Innovate idea 2; ability to see how the forecast impacts the project's profitability margin (i.e. if I resource a designer for 2 weeks, will this blow the budget). You could highlight the project red if it is no longer profitable and add the NET profit/loss value in the table or above/below the project name.This idea covers a number of improvement areas; we think this product is immensely important for all Workfront customers and will be welcomed by new customers as well.