Not Possible to Unapprove - Revision history

Alnaucler at 14:30, 23 September 2016

2016-09-23T14:30:22Z

← Older revision		Revision as of 16:30, 23 September 2016
Line 12:		Line 12:
	The most common reasons why it is not possible to Unapprove are:		The most common reasons why it is not possible to Unapprove are:
	* there are other items linked to the item		* there are other items linked to the item
	: The other items may be ~~approved~~ or in the workbench		: The other items may be Approved or in the workbench

Alnaucler at 15:59, 9 August 2016

2016-08-09T15:59:59Z

← Older revision		Revision as of 17:59, 9 August 2016
Line 1:		Line 1:
			{{Warning\| The Unapprove feature should '''NOT''' be used to correct or delete data because if you use Unapprove Action then all traceability and transparency are lost.
			If you need to correct data, you should create a new Data Entry Form using the '''[[Update from Summary Window \| Update]]''' action.

			If you need to delete an item, you should create a new Data Entry Form using the '''[[Delete from the Summary Window \| Delete]]''' action.
			}}

			[[Image:Inactive Unapprove.png\|300px\|center]]
			<div align="center">
			'' Inactive vs Active button''
			</div>
			When the [[Unapprove a Data Entry Form from the Summary Window\| Unapprove]] button is inactivated then it is not possible to Unapprove that Data Entry Form.
	The most common reasons why it is not possible to Unapprove are:		The most common reasons why it is not possible to Unapprove are:
	* there are other items linked to the item (approved or in the workbench)		* there are other items linked to the item
	* something is wrong in the Link table		: The other items may be approved or in the workbench
	* ~~trying to Unapprove a DEF~~ that is not the last one in an updating chain
	* the DEF is linked to another DEF but Date of Information are not chronological.
	Example 1 ~~(Albania)~~		* there are other Data Entry Forms that are updating the item with later dates i.e. is not the last one in an updating chain
	: ~~Victim-1 has~~ Date of Information ~~2013~~-11-23.		: Example 1: an Accident was created and approved with ''Date of Information'' '''2014-02-14'''.
	: ~~Victim~~-2 with Date of Information ~~2013~~-10-~~29 is linked to Victim-1~~.		: Later the Accident is updated with ''Date of Information'' '''2014-02-20''' and with a third Data Entry Form which has ''Date of Information'' '''2014-05-05'''.
	: ~~User~~ is ~~trying~~ to Unapprove ~~Victim~~-~~2 but is getting error message because Victim~~-~~1 is~~ newer ~~than Victim-2 based on~~ Date of Information.		: It is not possible to Unapprove the Data Entry Form with '''2014-02-20''' due to it exists Data Entry Forms with newer Date of Information.
	~~: The reality was that Victim-1 should had Date of Information 2012-09-23. After correction by SQL of Victim-1's Date of Information it was possible to Unapprove Victim-2.~~

	~~Example 2 (Ecuador)~~		* the Data Entry Form is linked to another Data Entry Form but Date of Information are not chronological.
	QM is linked to ~~Land~~. Land ~~has~~ Date Of Information 2003-11-27 and QM 2000-02-28 ~~then Unapproving~~ the ~~QM will not work~~.		: Example 2: a Land was created and approved first with ''Date Of Information'' '''2003-11-27'''.
			: Later a QM was created and approved with link to the Land but the QM Data Entry Form has ''Date Of Information'' '''2000-02-28'''.
			: It is not possible to Unapprove QM due to the Land has newer Date of Information.

	~~{{NavBox Hub}}~~		Contact your [[Information Management Team \| GICHD IM advisor]] if you would like to use Unapprove and the rules above should not preventing you from doing so.

	~~[[Category:NoPublic]]~~		{{NavBox Technical Notes}}
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 19:19, 8 August 2015

2015-08-08T19:19:20Z

← Older revision		Revision as of 21:19, 8 August 2015
Line 4:		Line 4:
	* trying to Unapprove a DEF that is not the last one in an updating chain		* trying to Unapprove a DEF that is not the last one in an updating chain
	* the DEF is linked to another DEF but Date of Information are not chronological.		* the DEF is linked to another DEF but Date of Information are not chronological.
			Example 1 (Albania)
	: Victim-1 has Date of Information 2013-11-23.		: Victim-1 has Date of Information 2013-11-23.
	: Victim-2 with Date of Information 2013-10-29 is linked to Victim-1.		: Victim-2 with Date of Information 2013-10-29 is linked to Victim-1.
	: User is trying to Unapprove Victim-2 but is getting error message because Victim-1 is newer than Victim-2 based on Date of Information.		: User is trying to Unapprove Victim-2 but is getting error message because Victim-1 is newer than Victim-2 based on Date of Information.
	: The reality was that Victim-1 should had Date of Information 2012-09-23. After correction by SQL of Victim-1's Date of Information it was possible to Unapprove Victim-2.		: The reality was that Victim-1 should had Date of Information 2012-09-23. After correction by SQL of Victim-1's Date of Information it was possible to Unapprove Victim-2.

			Example 2 (Ecuador)
			QM is linked to Land. Land has Date Of Information 2003-11-27 and QM 2000-02-28 then Unapproving the QM will not work.

	{{NavBox Hub}}		{{NavBox Hub}}

Alnaucler: Created page with "The most common reasons why it is not possible to Unapprove are: * there are other items linked to the item (approved or in the workbench) * something is wrong in the Link tab..."

2015-07-03T16:48:26Z

Created page with "The most common reasons why it is not possible to Unapprove are: * there are other items linked to the item (approved or in the workbench) * something is wrong in the Link tab..."

New page

The most common reasons why it is not possible to Unapprove are:
* there are other items linked to the item (approved or in the workbench)
* something is wrong in the Link table
* trying to Unapprove a DEF that is not the last one in an updating chain
* the DEF is linked to another DEF but Date of Information are not chronological.
: Victim-1 has Date of Information 2013-11-23.
: Victim-2 with Date of Information 2013-10-29 is linked to Victim-1.
: User is trying to Unapprove Victim-2 but is getting error message because Victim-1 is newer than Victim-2 based on Date of Information.
: The reality was that Victim-1 should had Date of Information 2012-09-23. After correction by SQL of Victim-1's Date of Information it was possible to Unapprove Victim-2.

{{NavBox Hub}}

[[Category:NoPublic]]
[[Category:NAA]]