The history API command returns all the changes to item records, from a specified point in time to the current time.<\/p>\n
http:\/\/www.myserver.com\/evj\/ExtraView\/ev_api.action? The <\/span>timestamp<\/span> <\/span>refers to the ITEM.LAST_DATE_UPDATED and the ITEM_HIST.LAST_DATE_UPDATED fields in the database. It is provided within the command in a value of any valid format allowed by ExtraView. If the value supplied can be misconstrued, the user\u2019s locale is used to determine the meaning of the date.<\/p>\n The <\/span>cutoff timestamp<\/span> <\/span>provides the current value of the fields. The <\/span>cutoff timestamp<\/span> <\/span>value is not included in the issues generated by this command; that is, the comparison is <\/span>item timestamp is greater than cutoff timestamp<\/span>. The <\/span>cutoff<\/span> <\/span>parameter is required.<\/p>\n The <\/span>cutoff_end<\/span> <\/span>parameter is optional. If omitted, there all issues up until the current time are retrieved. If provided, the value must be greater than the value of <\/span>cutoff<\/span>. This can be used to limit the items for which history is generated to a specific time period.<\/p>\n The <\/span>evhist_sellist<\/span> <\/span>parameter is a comma-delimited list of field names. This is an optional parameter, and if provided is a list of the fields that are output by the command. If it is not provided, the field list is taken from the detailed report of the user\u2019s current business area and project.<\/p>\n hist_range_start<\/span> <\/span>and <\/span>hist_range_end<\/span> <\/span>are optional parameters. If omitted, then the items retrieved are generated based upon updates that occured between these times. If provided then the query becomes a range query, where <\/span>hist_range_start<\/span> <\/span>is the beginning time and <\/span>hist_range_start<\/span> <\/span>is the end time of the updates to the records retrieved.<\/p>\n The optional parameter <\/span>username_display<\/span> <\/span>may be used to override the behavior setting named USERNAME_DISPLAY, for the duration of the execution of a single API call. This allows the developer to return the user names in a different format than the system-wide default.<\/p>\n dd_name_n=value<\/span> <\/span>represents an optional list of name value pairs to be used as filters on the query that returns results for the command.<\/p>\n The fields returned by the command are formatted as XML data.<\/p>\n The fields returned in the XML data are subject to two restrictions. The user must have read permission for the field, and the field must exist on the detailed report layout for the user\u2019s current area and project settings.<\/p>\n The item fields returned by the command are in the same XML format as those returned by the API get command.<\/p>\n The optional The item fields returned may contain repeating row data within the XML. If a deleted item record is encountered in the returned data, this will be shown in the XML as follows \u2013<\/p>\n <DELETED_RECORD ID=’item id’ FULL_TIMESTAMP=’issue timestamp’\/><\/span><\/p>\n This command provides a convenient method of determining all changes to the ExtraView database since a point in time, to be used to synchronize data with another ExtraView instance, or with a completely separate application (For example, ExtraView enables the synchronization of data with the Perforce SCM system with this command).<\/p>\n","protected":false},"excerpt":{"rendered":" The history API command returns all the changes to item records, from a specified point in time to the current time. SYNTAX http:\/\/www.myserver.com\/evj\/ExtraView\/ev_api.action? user_id=username &password=password OR [&access_token=token-value] &password=password &statevar=history &cutoff=timestamp [&cutoff_end=timestamp] &evhist_sellist=selectionList [&hist_range_end=timestamp] [&hist_range_start=timestamp] [&username_display=ID | LAST | FIRST] [&dd_name_n=value] [&show_attributes=YES | NO] NOTES The timestamp refers to the ITEM.LAST_DATE_UPDATED and the ITEM_HIST.LAST_DATE_UPDATED fields in the database. It is…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":24223,"menu_order":52,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_lmt_disableupdate":"no","_lmt_disable":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"class_list":["post-24259","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\n
\n\tuser_id=username
\n\t&password=password<\/span> <\/span>OR <\/span>[&access_token=token-value]
\n\t&password=password
\n\t&statevar=history
\n\t&cutoff=timestamp
\n\t[&cutoff_end=timestamp]
\n\t&evhist_sellist=selectionList
\n\t[&hist_range_end=timestamp]
\n\t[&hist_range_start=timestamp]
\n\t[&username_display=ID | LAST | FIRST]
\n\t[&dd_name_n=value]
\n\t[&show_attributes=YES | NO]<\/span><\/p>\n\n\tNOTES<\/h3>\n
access_token<\/code> parameter allows you to use a valid OAuth2 token obtained with the get_token<\/code> command. If you provide the access_token<\/code> parameter, then the user_id<\/code> and password<\/code> parameters should not be provided. This prevents the password being sent in clear text over your network connection.<\/p>\n