I didnât mean they were linked to order I mean an action like update order needs some form of link to an order such as being on a order level mapped automation command so an order is selected.
How do you mark them complete in the first place? Presumeably selecting the task on the screen, so I would suggest temporarily changing so selecting on screen fires that complete=false which will if it works tell you the action is working but you update all isnât meaning itâs the triggering method rather than the triggered automation itself.
I wasnât sure if you got it to work or not. Iâve been trying a few things since you posted yesterday.
I think what needs to be done is create a new task from a completed task.
This is what I was thinking:
However when I try to run the {REPORT TASK DETAILS:T.Name:T.Identifier=[=CommandValue]} it doesnât show anything. Iâm not sure what the proper syntax is to get the report tag to input into the new task to be created. Iâm using the highlighted text below to pass along Identifier ( {RANDOM} value from the task to be set to completed) as a CommandValueâŠeven though Id should be a lower character count.
Correction for the above image {REPORT OPEN TASK DETAILS:T.Name:'Identifier.Contains("[:CommandValue]")'} {REPORT OPEN TASK DETAILS:T.ContentText:'Identifier.Contains("[:CommandValue]")'}
I found an error in my settings. The report tag for âDaily Task-Addâ action should be:
{REPORT OPEN TASK DETAILS:T.Name:âIdentifier.Contains(â[:CommandValue]â)â}
{REPORT OPEN TASK DETAILS:T.ContentText:âIdentifier.Contains(â[:CommandValue]â)â}
Iâve made a correction note on my above post.
The incorrect report tag will not show any info after a work period has be closed and a new work period started.
Hi Bob, finally got time at work to go though this.
So I just want to get things right here. The RULE that you created Update & Copy New, I can run on a trigger at teh end of the day/week/month to reset the tasks back to Completed: False?
The way Iâve shown above it will mark the the task as completed. Then create a new task creating a new Identifier ({RANDOM}), then run 2 reports to get the Name & Content information, from the completed task, an insert in the appropriate fields of the new task.
My thinking of doing it this way would be for reporting purposesâŠAlthough, Iâm having trouble running a report for completed tasks. There might be a way, but I havenât found it yet.
This one uses tabs to separate the different tasks by states.
The basic overview on how it works:
Task is created and set to a state of âReadyâ. The âUnfinished Daily Tasksâ tab will display on tasks with a âReadyâ state.
When a task is marked as âFinishedâ it will record the date, time, user and change the state from âReadyâ to âSuspendedâ of the task state. It will then show up on the tab, âFinished -Daily Tasksâ. The âFinished Daily Tasksâ tab is set to display tasks with a state of âSuspendedâ.
When a task(s) is set to Reset, a new task will be created from the âSuspendedâ task, copying the task name, description and set the task state as âReadyâ as well as create a new unique identifier for the new task. It will also change the state of the âSuspendedâ task to âFinishedâ.
Then the process starts over.
I also added a little security. Only âAdminâ can create and edit tasks. If your user roll is âAdministratorâ or something different, you will have to change to constraints on the rules:
DailyTask-Edit Task Step 1
DailyTask-No Permission
& the âAdd a Taskâ button on the entity screen. (Property Editor -> Validation field. It is currently set as '{:CURRENTUSERROLE}' == 'Admin'
I used custom fields that were defined in Actions. The only predefined field I used was Identifier. Through my learning, I found that I could control the display of custom fields in the âTask Editorâ. I was could not figure out a way to display the predefined fields, other than the standard way. I also tried to stay way from using the word âCompletedâ, not to be confusing with setting the task predefined field as Completed = True. I was not able to access the task through Reports when a task was set as Completed = True. Having said that, all tasks that have a status of âFinishedâ will have a Completed = False. I donât know what effects that will have on the database over time. If a task has to be permanently removed the word âCompleteâ can be added to the Task Editor ->Property Editor->Task Commands box.
Here is the import file: DailyTasks.zip (3.6 KB)
The first 2 times I imported the file, one of the Task Editorâs would be missing. First one was âUnfinished Daily Tasksâ the other was on the âFinished Daily Taskâ. The 3rd time, everything imported correctly. If you, or anybody, has trouble, let me know. I will post the fix.
I would appreciate some/any feedback from anybody looking at this. I know there is some improvements that could be madeâŠparticularly the report. After I get feedback I will make a tutorial out of this.