Use Asana to separate task notes from a decision
Example: A task note records a customer's proposed change. The due date remains the original accepted date.
Keep Asana as the source for its records. A Righthand can use available information for the decision below.
This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.
The customer task
A task note records a customer's proposed change. The due date remains the original accepted date.
Provider documentation. The documentation gives information about task properties, assignees, dates, completion, and project memberships. These properties give different task facts.
Make account access explicit
If Asana is available in Connections, connect the intended account. Give the Righthand access to that connection.
Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.
For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.
Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.
The request to the Righthand
Read the supplied task and customer note.
>
Send the proposed change independently from accepted dates.
>
Prepare the decision question for the owner.
>
Send the owner the result before 3 PM Friday.
>
Use Pacific time.
Use the provider records for the result
Identify the task and project. Compare the task's assignee, dates, and completion independently. Prepare changes only for the property that the owner approved.
A note can contain a proposal without approval.
For a permitted write, examine the resulting account record. A proposal does not establish a completed change.
For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.
An illustrative result and next step
The customer proposes Tuesday delivery. The task still carries the accepted Friday date.
The owner gives a decision about the new commitment before the assistant changes the due date.
Try one account task
- Give the Righthand one identified source record.
- Compare its result with that source.
- Examine the account record after a permitted write.
- Examine the work in Activity.
If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.
When the account tools are sufficient
Use Asana directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.