10

Currently, the only fields the Agreement Booking Setups default to are the Start Date and End Date of the parent Agreement Entity. The other fields: Recurrence Patterns and Range of Recurrence (except Start Date) all have to be entered manually on each Agreement Booking Setup. (and Recurrence Pattern XML does not appear to accept XML generated via Workflow) It would be helpful if they were instead drawing from explicit Agreement Booking Setup fields (that don't necessarily have to be displayed to Users), so that those fields could be prepopulated by organizational defaults or set by Workflows to reduce data entry burden for Users on each and every Agreement Booking Setup. For example, if a User is allowed to select a Weekly recurrence pattern and the company only works a Mon-Fri schedule, the Days fields could be preset by Workflow to prepopulate on the Booking Recurrence form, saving the User 5 clicks per Agreement Booking Schedule. The User would still have the option to override the defaults manually. If a User selects End Recurrence to be Never, After, or By, different fields would appear - for After, the Number of Occurrences, for By, a Date field. These would populate the appropriate fields in the Recurrence Dialog. This doesn't seem like a huge click savings, but consider that these fields could be prepopulated by Workflow and thereby saving considerable data entry.

Category: Field Service
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for your feedback. We really like this idea. We are doing work in some related areas and may take the opportunity to look at some of this, depending on complexity.

At the moment, by itself, this is not currently in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.

Thanks, Boris.

Jason Cohen
PM, Microsoft

Comments

B

Something that is a problem for us is that you cannot just have custom booking dates without setting a recurrence pattern.

Category: Field Service