Jeto Ideas

My thought is upon approval, all fields would be locked. Then, when editing needs to be done, the field or fields being edited would be individually unlocked to make the changes. They would be locked again upon resubmission.

This would help to ensure that only the specific fields would be getting updated with little chance for other fields to be changed or overwritten.

We have many cases where the launcher needs to be submitted weeks before all of the content and details are available. We would like to have the submitter go back into Jeto to add information as it becomes available but have been hesitant to push the edit features to the submitter because we are afraid that other data may be overwritten. Currently, the ongoing updates are done manually by operations.

One other note on this comment, there could be situations where the team does not want to use the approvals process, but instead block updates from happening after a certain amount of time, which we could put as either an account or launcher setting

• to add this feature: make the fact that collaborators can approve their own campaign an account feature. Not all customers want their collaborators to have that option but I other customers do if the approval happens outside of Jeto (so the user can keep track of his own statuses)

David, the use case was for the entire content. It was reviewed by several people and approved and the emails were scheduled. We want to prevent users from then making last minute changes that won't be noticed by admins and emails going out with something that was unapproved. So no, no "oops" moment because several people went through the process of reviewing and approving.

FYI - this idea is still "private"

I think this should be independent of the approval process. Some people want to auto launch campaigns, therefore cannot use the approval process but still want people to stop making edits.

I also think this should be a launcher setting (if too complicated, an account setting) and I can train users and admins on it. If you activate it, you are agreeing that those "oops" moments will be on your team to manage, not Jeto. If you don't, then allow for changes.

Thanks Cat. I'd like to clarify a couple things:

• Do you expect the approval to be global to the entire form/data, per data point (input field) or per asset?

• Also, from my experience there is often a "oops" moment where you realize there is a typo on an approved asset. In this case what would be the process to fix this?