Example: Detect updates and initiate project

Take the example that you want to be notified and have a new project created for any new or changed assets in your top-level source folder (/Web/English). You want WorldServer to check for new or changed assets every night at 1:00 am.

Set up a workflow for which you want to create a rule.
Create a recurrence named Daily-early-am that runs every day at 1:00 am.
Create a new rule that specifies what you want to occur. The final rule will look something like the following in the Rules Wizard:
For all new or changed assets under /Web/English, email the list of assets to jdoe@company.com using subject Changed assets and initiate project New Material for locales German and French and workgroup default and workflow Web Updates . Execute this rule on schedule Daily-1am.The name of this rule is Detect changes and initiate project.

When the rule executes, WorldServer looks at the path specified and creates a project per locale when it finds modified assets. These projects contain tasks for each asset modified.

Note: When the action is Initiate Project, you are prompted for the new project name. If you just supply text, such as New Material, every project created by this rule will have that same name. If, for tracking purposes, you want each project that is created to have a unique name (instead of just a unique project number), you can add ${id} to the project name you specify in the rule. If you were to specify ${id} New Material as the project name, each project created by the rule would have a different name, for example:

2112 New Material
2113 New Material
2114 New Material

and so on. Be aware, however, that the number appended in the project name does not correspond to the project number assigned to that project. You might have a project named 2113 New Material that has a project number 2102.

The rule also causes WorldServer to send an email with a list of the new and changed assets to the specified user (jdoe@company.com).