I was assigned with a task. The task is to allow certain fields in a custom list in a subsite, to have the value auto-generated based on the entered name, plus to hide those fields when creating New Item.
For fastest result with minimum effort, I decided to use SPD for this task. I specifically love the Workflow Designer in SPD.
- I designed a workflow, to be executed when a new item is created to auto-generate the values using Build Dynamic String action.
- To hide the field when new item was created, I modified NewItem.aspx form, removed the ListForm webpart and add in custom list form and it work flawlessly within 15 minutes.
When to use SPD ?
- Fast result, minimum effort situation like proof-of-concept, demo to impress the clients !
- Train the trainer basis project in which power users are educated to self-sufficient
- Layout and user interface design
- Site specific customizations
- Customization involves multiple sites deployment
- Component-like generic workflow, to allow flexible configuration and cross list implementation
- Event-driven customization
- other things that SPD accomplish or too tedious to perform
Guess I will have to learn both of the tools to become a real SharePoint sensei ?
No comments:
Post a Comment