I have a rule that creates subtasks once the Task is created by the user.
I have one more rule that checks the fields in the Task and change the status of the relevant subtasks.
After creating the task Rule 2 is executing faster than Rule 1, and because of this the status of the subtasks are not updating based on the field value in the task.
Related
Using the simple pipeline layout above, I want to be able to selectively run any or all of the activities to the right of the If Condition activity based on a parameter value. Or is this an "all or nothing" execution?
Like if the parameter is 3 then run the stored procedure and function but not the other two or if the parameter is 5 then run all but the function or if the parameter is 8 then only run the function and so on to however many scenarios required.
Thus far, the only way I am able to make this work is to give each activity on the right its own If Condition activity and put a Fail activity inside the "False" activity for each of those If Condition activities where the parameter doesn't check out.
You can use switch activity wherein you can use a single expression based on multiple if expressions for your different use cases
https://learn.microsoft.com/en-us/azure/data-factory/control-flow-switch-activity
I'm importing all the tasks from outlook into a database.
To flag those that are different since the last import I need a unique ID for each task item object that does not change.
I've looked at TaskItem.EntryID. The microsoft documentation says it's only unique to each storage location which is fine as these tasks won't be moved.
The trouble is with recurrences:
I make a recurrent task due on 28/05/2019 which has an ID of ..D890000
I complete the task and outlook creates the new task for the next scheduled day.
The original task for 28/05/2019 now has a DIFFERENT ID of ..D8A0000
The new task for 29/05/2019 has the original ID of ..D890000
I have also tried using PR_SEARCH_KEY which is the same across these tasks.
Would anyone be able to tell me how to get a unique ID for each TaskItem that persists.
Or would you be able to confirm that the only time it will change is in the event of recursive tasks?
Many Thanks
It works as expected - when an instance of a recurring task is completed, Outlook creates a completed task for the current date and advances the existing recurring task to the next day while decrementing the recurrence count.
enter image description here
I'm trying to find an efficient way to select all dependencies. The idea behind this table is:
Each taskID is a task that will be display to the user.
When taskid 22180 is selected by the user and completed it will
automatically enable the other tasks (activateTaskId = 22180) to
become available to the user hence inactive = 0. Up to that point
everything is fine.
What i need help at is when you have subsequent tasks.
So when taskid (22180) is selected and completed by the user the following tasks become available (22181,22182,22185 and 22186). As you can see if the user selects 22182 then the task dependent on it is 22183 and subsequently 22184 will .
how would i efficiently select all the task that branch off the initial one (22182) no matter how many may exist ?
Thank you
I am looking to see if its possible to have one job that runs different schedules, with the catch being one of the schedules needs to pass in a parameter.
I have an executable that will run some functionality when there is no parameter, but if there is a parameter present it will run some additional logic.
Setting up my job I created a schedule (every 15 minutes), Operating system (CmdExec)
runApplication.exe
For the other schedule I would like it to be once per day however the executable would need to be: runApplication.exe "1"
I dont think I can create a different step with a separate schedule, or can I?
Anyone have any ideas on how to achieve this without having two separate jobs?
There's no need for 2 jobs. What you can do is update your script so the result of your job (your parameter) is stored in a table. Then update your secondary logic to reference that table. If there's a value of parameter, then run your secondary logic. All in one script. If there's no value in that parameter, then have your secondary logic to return a 0 or not run at all.
Just make sure you either truncate the entire reference parameter table every run or you store a date in there so you know which one to reference.
Good luck.
I have a list called "Tasks"with a number column called "Count".
On the "Workflow Tasks" list, I have a workflow that gets triggered on item added or item changed. When a workflow task is created/edited, the workflow checks the status of the task and either adds 1 or minuses 1 to the "Tasks" "Count" column.
If I add a single task to the workflow task list, the workflow picks it up and adds 1 to the "Count" field perfectly. However, if i add two tasks to the workflow task list, one after the other, the second task's workflow results in an error.
It's almost like i'm unable to update the "Count" field multiple times. I assumed that the row was somehow "locked" while the first instance of the workflow was updating it, so I added a pause, which didn't help. (I guess because the 2 instances pause at the same time.) I then added another column to the "Tasks" list called "Busy" and set this to "Yes" while the first instance updated the row. When the second instance runs, it first checks if "Busy" is "Yes" and if so, it pauses for a duration and then carries on. This still does not work.
Is my assumption of row locking correct? Or what am I missing?
TIA!
Edit: I don't have access to the error logs and the error simply states "An error has occurred in [Workflow Name]".
do you have many workflows and only one task to change? workflow runs, when task is changed or workflow list is changed?