It would be great to have an admin permission that allows users to edit fields that are set as 'non editable' in the field definition. It is very time consuming when testing to have to navigate to the workspace manager and change the field properties. It would also be a useful feature to have as an administrator to make changes and corrections easily.
It seems useful (to me) to be able to control section expand/collapse within a script. Tying that to workflow steps - expanding / collapsing as I move through the stages of a workflow - would be able to expedite actions and focus users.
It would be the coolest thing ever to see the rest of the transition properties on the Workflow Summary Panel. When you have 73 transitions like I do It would save a lot of time to be able to see which scripts were tied to each transition, or to make sure that there is a script tied to the transition.
This Idea kinda is a double edged sword. First the use of picklists, both standard and Workspace Types allows a great deal of control over user input when used to limit what can be entered into fields when completing forms.
But there are times when allowing the user to add a new record to the picklist on the fly is also desirable.
Use case is for say a sales bid log that is used to support a quoting workflow. As the salesman get requests for quotes from various customers it becomes tedious to make it a two step process to enter the bid request in the log.
Step 1, see if the customer exists in the customer workspace, if not add it
Step 2, Add the new bid record using the new customer record.
I have been working on several methods to allow the bid log to get entered and use scripting to validate and add the new customer record to the customer workspace. This works but is clunky in that you have extra fields in the bid log that make editing the record clumsy.
It would be nice to have a feature that would allow for new records to get added to the connected workspace if they did not exist.
Not sure the best way to approach this and would guess that scripting would need to be involved. But the basic idea:
if when entering/editing the record that has a workspace based picklist, if the value entered does not exist in the pciklist workspace.
1. Have an Option to add the record, either
a) Similarly to adding linked items records through a pop up or
b) Through a checkbox or some other scripting validation to verify or prompt the user they are about to add the new record
When I send an email I would like to be able to add in an .ics file.
The .ics file a simple text file contains information about a meeting or event. the .ics file's contents are understood by outlook and other calendar packages. Clicking the ics file in the email adds the meeting or event to you calendar.
How I think this could be done,
in scripting the Email() object should have some more options for create .ics file and the values to go into it, The information in the .ics file is event name, start date/time, end date/time, location, title. you could then grab / map item fields such as date, time location event, and map them to the .ics file. this would populate your calendar with the meeting or event.
We would like to be able to narrow down a linked picklist for a certain criteria.
Example: We use Product ID as a unique identifier for products. In other workflows, we will link a picklist of Product IDs to a form so that we can assign more attributes to the product. Product ID can have a status of "Assigned," "Orderable" or "Retired." We would like to pre-filter a picklist of products to show only those that are in status "Assigned" but not "Orderable" state. There is no current client-side scripting available today.
Only possible by "chaining" workspaces. Create a new picklist when the item changes status, e.g., when a Product ID is first released, spawn record in another workspace with the narrowed-down population of "Assigned." .
Based on a value or status of a field, the ability to take an action based on changes to a field value.
Example, moving to the next step in the workflow. In the process to create a product name, the Person A asks Person B to create a name and get it approved by Legal. If Person B approves a product name, we would like the workflow to automatically advance to the next stage based on the "approved" status so that there are less clicks for the user and less chance of forgetting to advance the workflow on the Workflow Actions tab.