Hello:

I am using CRM 3.0.  I would like to use workflow manager to monitor several 
bit type attributes.  Basically when a check box is checked in a specific 
entity I want an email notification and/or other workflow events to happen.  
I am successfully performing this with a simple "wait for" condition workflow 
rule assigned to each of the entities...when the checkbox is checked, I get 
an email.  Not all of the checkboxes will be used during the "active" period 
of the entity.  The problem that I am having is stopping the workflow rule 
when a particular entity is no longer active.  The Workflow Monitor is 
showing the rule as running even though the particular entity is inactive.  
After compiling hundreds or even thousands of these entities won't that cause 
a lot of overhead on my CRM server?  Should I be concerned?  If so, is there 
a way to end the workflow rules for entities that are inactive?

The best way to handle this would be to re-create this workflow as a manual 
rule. Then, using a Create worflow, call the rull as a subprocess. Then add 
another wait for timer to wait until the status is "Inactive", then close it 
using "Complete and stop processing other rules". This should end your 
Subprocess (which waits for the checkbox) as well as the parent rule.

"BJME" wrote:

> Hello:
> 
> I am using CRM 3.0.  I would like to use workflow manager to monitor several 
> bit type attributes.  Basically when a check box is checked in a specific 
> entity I want an email notification and/or other workflow events to happen.  
> I am successfully performing this with a simple "wait for" condition workflow 
> rule assigned to each of the entities...when the checkbox is checked, I get 
> an email.  Not all of the checkboxes will be used during the "active" period 
> of the entity.  The problem that I am having is stopping the workflow rule 
> when a particular entity is no longer active.  The Workflow Monitor is 
> showing the rule as running even though the particular entity is inactive.  
> After compiling hundreds or even thousands of these entities won't that cause 
> a lot of overhead on my CRM server?  Should I be concerned?  If so, is there 
> a way to end the workflow rules for entities that are inactive?

Hi,

Create a workflow rule ( Change status ) and check condition whether the 
entity.status = inactive. If so set action to call a workflow assembly . In 
that workflow assembly   update the statecode (workflowprocess table)  as "4" 
for all the workflow process instance related to this entity.

I hope this helps

Ram

"BJME" wrote:

> Hello:
> 
> I am using CRM 3.0.  I would like to use workflow manager to monitor several 
> bit type attributes.  Basically when a check box is checked in a specific 
> entity I want an email notification and/or other workflow events to happen.  
> I am successfully performing this with a simple "wait for" condition workflow 
> rule assigned to each of the entities...when the checkbox is checked, I get 
> an email.  Not all of the checkboxes will be used during the "active" period 
> of the entity.  The problem that I am having is stopping the workflow rule 
> when a particular entity is no longer active.  The Workflow Monitor is 
> showing the rule as running even though the particular entity is inactive.  
> After compiling hundreds or even thousands of these entities won't that cause 
> a lot of overhead on my CRM server?  Should I be concerned?  If so, is there 
> a way to end the workflow rules for entities that are inactive?