Wait for condition not working in scoped application

rishika95
Tera Contributor

Hi, I have a workflow in a scoped application. The wait for condition activity doesn’t move ahead even if the condition is matched. The workflow is on table 1 and the updates are made to table 2. I even wrote a business rule to update table 1 status when table 2 status is updated. Nudging the workflow doesn’t help. 

2 REPLIES 2

Karthiga S
Kilo Sage

Hi @rishika95 

 

The issue you're facing might be due to the fact that the 'Wait for condition' activity in a workflow only listens for changes on the current record of the table where the workflow is running. If the changes are happening on a different table, the workflow will not be aware of it. Here are some steps you can take to resolve this:

1. **Create a Business Rule on Table 2**: This business rule should be triggered when the status on Table 2 is updated. The purpose of this business rule is to update a field on Table 1 that the workflow can listen to.

2. **Update the Workflow**: In your workflow in Table 1, update the 'Wait for condition' activity to listen for changes on the field updated by the business rule in step 1.

3. **Test the Workflow**: After making these changes, test your workflow to ensure that it's now progressing as expected when the status on Table 2 is updated.

4. **Debugging**: If the workflow is still not progressing, use the workflow context to debug and see what condition it's waiting for.

5. **Check for Errors**: Check the system logs for any errors related to the workflow or the business rule.

Remember, the 'Wait for condition' activity in a workflow only listens for changes on the current record of the table where the workflow is running. If you want your workflow to react to changes on a different table, you'll need to create a mechanism (like a business rule) to update a field on the current record when the other table is updated.

 

Please mark it Correct and Hit Like if you find this helpful!

 

Regards,

Karthiga

rishika95
Tera Contributor

Hi,

This issue was solved when i made gave an update command in BR which is on table2.

table1obj.update().