I have created a custom state machine workflow.When I am submitting the request using info-path form,workflow get started ,but no task is created in task list.
I tried to do manual entry in task list ,but still no item is added to task list.
How can I fix this problem? Is there any problem with my task list?
Related
I have a Mule 4 flow that uses the [File] On New or Updated File event source. This element is configured to wait for file changes within a specific folder.
When I deploy my flow, and the deployed application does not have access to the specified folder, a log message is generated and the flow terminates. However, I'd like to add some additional processing in this case. (I'd like to log a message to an alternative event log).
I tried adding an On Error Propagate element to the flow, but this is not triggered when the error occurs - I think this is because the error is a system error rather than a messaging error.
If I could add a step before the On New or Updated File element, then I could check for the existence of the folder, and execute that extra code there - but I see no way to do that either.
Well, I was able to do something that "works". I created another flow that runs on a (long) timer, which runs immediately and checks for the existence of the folder by attempting to list its contents. If that fails, then the On Error ... block of that flow is reached, because in this case the error is treated as a messaging error rather than a system error.
Not an ideal solution, but a solution nonetheless.
May I suggest that you monitor folder which should contain none existing folder?
For exmple you want to monitor /one/two/three/abc.txt. three does not exist. Watch two for new and updated files.
Trying to wrap my head around how a BPMN/CMMN model can be used in my application.
There are several CMMN User Tasks with Forms as part of my application BPMN process.
I use Embedded User Task Forms
The data submitted by my forms get stored in the task variables and passed out to the parent process using all to all variables mapping.
To progress with the process, the user needs to [claim task], fill out the form and then complete it (via a REST call).
After the User Task with the form is completed is disappears from the list of available tasks in the /task REST endpoint (as well as in the Admin UI).
But what if I'd like to show users the variables that they have submitted to their tasks before completion after they have completed the task?
First, I thought to use the Get Tasks (Historic) (POST).
And that works in a sense that I can see the metadata about the tasks completed by the users before.
But how can I see the variables and actually the HTML form that had been used at the point of task completion? That is, the data available via
/task/{id}/variables
/task/{id}/form
before the task is completed?
The response from /history/task contains neither variables nor the form key.
Trying to access the completed task by its id, like {{camunda}}/task/46386/form or {{camunda}}/task/46386/variables
results in
{
"type": "RestException",
"message": "Cannot get form for task 46386"
}
or
{
"type": "NullValueException",
"message": "task 46386 doesn't exist: task is null"
}
respectively.
I think that I am missing something basic here.
That is probably the principle of the BPMN engine. When tasks are completed, they are considered to be gone forever with no option to access its data later any more (except for basic audit log details)?
Another side-question is whether the task access permissions that were set up in the Authorizations apply to the results returned by the /history/task endpoint?
Update:
Found the way to access the historical variables: Get Variable Instances but not the historical Task form keys.
Found a similar question.
In one of the workflows, task notification has been sent to an user's inbox. When the user tries to acquire the task, he is getting the error like missing package for the current task of the workflow.
Kindly provide me the suggestion on resolving this issue.
During the Workflow definition if the Package is added as Mandatory Package, and during task completion process if the task attachment is missing, user is expected to get this message in D2 client.
Please check weather the Task attachment is missing from repository in this scenario.
You can either:
Verify if the associated activity definition for the task (from process builder for example) has defined correctly the package/s.
or
Verify if the attached object (document/s or folder/s) to the task exists in repository or the user has at least BROWSE permission on it.
Also, a good idea is to check the D2 app server and JMS logs.
I am using the Asana API to add tasks from a website any time a node on the website is added/edited. I am adding tasks to a specific project, and adding a custom field so I can map the task back to the node. When I add a task, I check existing incomplete tasks on that project to see if any have the same node. If I find a task for the same node, I take that task's ID and set it as the parent for the new task. That way I dont have a long list of the same task, but can tell if the node was updated again.
The problem is in the new subtask is if I set the project, this new subtask is added both inside the parent task (good) but ALSO shows up in the project list like its not a subtask (bad - defeats the whole point of making it a subtask to not clutter up the task list for the project). If I do NOT set the project for this new subtask, then I get an error "Custom field with ID xxxx is not on given object".
So how can i add this subtask without it showing in the project main list?
In Asana, subtasks don't inherit the custom fields of their parent task. However, it sounds to me that you maybe don't need the custom field on the subtask (because you have it on the parent task). So when you create the subtask, you could try not setting the value of the custom field.
If you really need the custom field on the subtask: when you create the subtask, you should be able to add the subtask to both the project and the parent task while setting the custom field (at this stage it will show up in the root level of the project and as a subtask, like you noted). Then in a second API action remove it from the project (using the POST /tasks/task-id/removeProject endpoint). Asana tasks retain custom field values even if they no longer belong to the project where they originally got that custom field value (as long as the value is set).
I get this error when I move the issue from In Progress to Done.
Workflow jetbrains-youtrack-scrum reports error: Cannot find State [Done]
Contact project admin admin
This was fine before, but has started behaving differently ever since the issue was also added to two boards.
Both the boards have "Done" as a valid status. What can be the problem?
This workflow may fail with such an error if it is not possible to set 'Done' state to a parent issue.
Thus, most probably, this particular issue is a subtask of some other issue from another project, which doesn't have a 'Done' state in its 'State' field values set.