When attempting to build automations against the ‘Requests > New’ webpage, it would be helpful to have a reference column for the RequestId itself.
Right now, the only way to see the ID is by clicking the ‘View Request’ and viewing it in the url.
Unique row IDs and or cell IDs would also be hugely beneficial when setting up web automations. As it is now, every cell gets one of two IDs, and each row gets an alternating class assignment.
Technically speaking, an ‘ID’ for an element on a web page should be unique.
If the id was built dynamically, it would be much easier to reference elements and setup automations.
IE: “rsl_date_<requestId>”, “rsl_requesttype_<requestId>”, “rsl_companyname_<requestId>”, etc.
Jessica Mayher
| How often would this idea be used? | Weekly |
| How much time would you save when the idea is implemented? | It would save a day of work |
| How many people at your company would benefit from this idea? | A Team or Group of People(5-25) |
|
What problem is your idea trying to solve?
Once we scrub the initial Influencer Add requests (check for first, last name, phone # and title) there is no need for our Gatekeeper's to review the information. All they are doing is clicking 'push to ERP' since there is no way for them to validate the information provided once it has been scrubbed. Our automation has eliminated hours of time from the gatekeeper. We feel it would be easier for others to implement if the backend was fully 'unique' and available to programmers. Future automations would be programmed and implemented much quicker if this data was available to us. |
|
