Postplan¶

Definition¶

<postplan>
...
</postplan>

A sequence of plan elements for bookeeping actions after a resolve goal has been resolved or downdated. Postplans are only available for resolve plans.

Parents¶

• <goal>

Children¶

• <assume_issue>
• <assume_shared>
• <assume_system_belief>
• <bind>
• <findout>
• <forget>
• <forget_all>
• <forget_shared>
• <get_done>
• <if>
• <inform>
• <invoke_service_action>
• <invoke_service_query>
• <jumpto>
• <log>
• <raise>
• <signal_action_completion>
• <signal_action_failure>

Behaviour¶

Immediately after a resolve goal has been fulfilled, the contents of a potential postplan element will be added to the plan in TDM. This is intended for bookkeeping tasks like assuming and forgetting propositions, possibly jumping to other plans etc. Since the goal has already completed, a jumpto inside a postplan does not need a guarding <once> or conditional to avoid looping.

Examples¶

Postplan for forgetting all propositions of the predicate attraction¶

<postplan>
    <forget predicate="attraction"/>
</postplan>

Postplan for keeping track of that a certain plan has been executed¶

<postplan>
    <assume_system_belief predicate="enrollment_done" value="true"/>
</postplan>

Postplan jump after a resolve goal¶

<goal type="resolve" question_type="wh_question" predicate="opening_hours">
  <plan>
    <invoke_service_query type="wh_question" predicate="opening_hours"/>
  </plan>
  <postplan>
    <jumpto action="offer_booking"/>
  </postplan>
</goal>