Use this menu to quickly perform an action on a need.
Note: on pages that list needs, clicking on a need name (a hyperlink) will perform the same action.
These commands are used to update the status of needs on your shopping list. In many cases they will either remove the need from the list or reduce its urgency -- that is, move it down the list -- by increasing its "days left".
If you actually did have more assets remaining than MakeLifeEasy indicated, and you "corrected" the amount left, the need will be moved down (or off) the current shopping list, since its "days left" will increase.
When you record a new asset that covers a need, the need will be moved down (or off) the current shopping list, since its "days left" will increase.
The postpone command can also de-activate an asset. This postpones it indefinitely ("forever") until you decide to re-activate it. You can do this if you think you'll shop for the need in the future, but you have no idea when, and you want to keep it in your database. Alternately, you could keep postponing it and postponing it, so that it shows up on your list every now and then. That way, you'll be reminded about it occasionally.
You can also enter "0" to "un-postpone" a postponed need.
If and when you want to "recover" (un-postpone or re-activate) a need, you'll want to know the difference between postponed and inactive needs.
A postponed need has an "Active" status, but it has a start date in the future. That's why it has "days left". It remains on your shopping list, but postponed. It will eventually rise up on your shopping lists again, when its start date approaches. Or you can un-postpone it using the Search Needs < page.
An inactive need has an "Inactive" status. It won't show on your shopping list until you re-activate it. You can re-activate it using the Search Needs < page.
You can temporarily hide a need if you just don't want to deal with it today (or you don't want it to show on a printout) and you'll deal with it the next time you sign in. For example, if you can't decide whether to delete or postpone a need, and you're not ready to cover it right now, just hide it. This removes it from your shopping list for this session only.
You can delete the need (and any assets covering it) completely from the database. Usually you would do this when you've added a need by mistake, or you've changed your mind about it. In any case, you'll never want to cover it (again) in the future.
The above commands are used to update the status of a need on a shopping list. The commands listed here are used to reorganize the needs on a shopping list. There are other ways to reorganize needs, too. For example, the Browse Needs < page is helpful for this.
You can quickly change the name of a need with this command. However, keep in mind that this should be used to refine a need's name, not change it to another need, especially if (1) the need was created from a standard need, or (2) the need already has assets associated with it. For example, if you had a need for "Red apples", but now your need is more (or less) particular, you might want to change its name to "Washington red apples" (or just "Apples"). However, don't "re-use" a need by just overwriting the name. That is, don't change "Apples" to "Pasta". Instead, delete "Apples" and create a new need named "Pasta".
This command pops up the Move Multiple Needs setup page. Using the setup page:
The needs you checked off will be moved to the "target" folder.
You use this command to organize your needs. For example, you may have started out with a simple set of folders that you now want to make more specific. That is, over time, your set of folders will grow and change, and you may need to split sets of needs between folders in this new folder set.
All the assets of both needs will be combined under the one "chosen" need, and the "unchosen" need will be permanently removed from your database.
You use this command to organize your needs. Over time, two different needs may become the same need. Or, you may realize at some point that two different needs are the same need.
For example, say you have (mistakenly) created two needs for "Paper towels": one under "Cleaning" and one under "Food", and you have entered assets to cover both. They are really one and the same need, and they should be combined so that the assets covering them will add up to provide the correct days left value.
(To use this page, both the "source" and "target" needs must already exist. If the "target" doesn't exist, create it first, then return to this page.)
This command pops up the Split One Need Into Two setup page. Using the setup page:
The assets you checked off will be moved to the "target" need.
You use this command to organize your needs. You may have started out with simple needs that you now want to make more specific. That is, over time, a need may need to be broken out into multiple needs that are more specific.
For example, say you have created a need for "Fruit", and you have entered "Apples", "Oranges", and "Pears" as assets that cover the need. Now you've decided that you want to break these out into multiple needs, for example, to specifically test the prices that different stores charge for each. Create needs for "Apples", "Oranges", and "Pears", and split the assets among those needs.
This command pops up the Need Shopper page to help you shop to cover the need from sellers in the database.
NOTE: In the Image Management System, the "Shop" function is still in development. If you're using an agent, ask them for assistance.
When you check this box, some of these commands will refresh the calling page
(e.g., the shopping list) after performing the requested action.
Specifically, the Postpone, Hide, Delete, and Rename commands will refresh the calling page when you check
this box before executing the command.
For other commands, you can usually press the "Go" or "Refresh" button on the calling page
to show updated results.