Make policy creation use case easier

When creating a policy there are 3 very common stumbling blocks that force them to abandon the definition and start over from step 1. These problems are, roughly in order of occurrence:

***** A. User forgot to define tag for the policy. Currently, the user must
i. cancel the policy creation,
ii. navigate to tags tab,
iii. create the tag(s),
iv. navigate back to the policy tab,
v. restart the policy creation from scratch

Request is to extend policy creation sequence to allow user to create tag(s) as part of the policy definition step(s) - WITHOUT having to exit and redefine policy.


***** B. For content-search policies, allow user to create regular expression(s) as part of the policy creation sequence. This is very similar to (A) above. Today, if the regular expression does not exist, then user must abandon policy creation, go to regular expression tab, create a regex, and restart the policy creation sequence from scratch. This requires at least as many steps as outlined in (A) above.


***** C. Do not terminate a policy creation sequence with autologout. This is very frustrating for everyone. Frequently, we will be showing customer how to create a somewhat complex content-search policy and get to the schedule or review step only to have the FINE appliance log us off entirely, losing all of the policy definition work that's been done.