Explore

Search
Blog Index

How to > Concepts and Background > What is indenting and association?

Search the FAQ for entries containing:

MeetingGold uses document parts as the basis for its documents. Often a document part can stand alone and doesn't need any supporting document parts to travel with it. However, it is often the case that you need to keep a bunch of document parts together. For example, if you have a few actions that are closely related and combine to complete an overall task, you would want to keep the tasks together so that you could review them as a set.

Association of document parts is a very powerful feature in MeetingGold. Document parts can be associated with each other in a heirarchical structure. The document part at the top of a heirarchy is the head document part. You can associate other document parts with the head document part by indenting them to the right in the document with a swipe of your finger. You can disassociate them by swiping back to the left.

Association is probably best illustrated by way of an example:

Suppose Steve Baldwin the Sales and Marketing Director has been asked by the Board to report back on progress on project X. He needs to delegate the project to his Sales Manager, Kendrick Cook and to his Marketing Manager, Rachel Dawkins.

He sets up a meeting with them both, bringing his action from the board meeting into the new meeting document. During the meeting with Kendrick and Rachel he gives them an action each (see screen shot below):

As you can see, when Steve entered the new actions he swiped them to the right and they are both shown indented slightly and under the menu icon  there is an indication of their indentation level (in this case 1 as they are both one level deep - you can go to any depth).

Steve has now delegated the task to Rachel (the marketing aspect) and Kendrick (the sales side).

Now, Steve sends this meeting document to both Kendrick and Rachel and they carry out their actions and update their progress on their iPads. At some point later they send those actions back to Steve either in the document they originally received or maybe in a totally different document e.g. if he has chased actions by email. If Steve then opens his original document or a new document with his original action in it he will see the screen shot shown below:

As you can see the actions for Rachel and Kendrick are grayed out - meaning that there are more up-to-date versions available. In the screen shot above Steve has tapped on Rachel's action and is being told that he can get a more up-to-date version. He taps on 'yes' and does the same for Kendrick's action resulting in the screen below:

On this screen Steve can see the updates that both of them have made describing where they are on this action. Notice that both of their actions travelled independently, were updated independently and have been recombined at the right time for Steve to view. They were easily combined because they were associated with Steve's original action which allowed him to track them easily.