KB44197: Warehouse tables for Mobile clients in MicroStrategy 9.x and 10.x

• Strategy

Warehouse tables for Mobile clients in MicroStrategy 9.x and 10.x

Introduction:
Collection of Mobile Client statistics is a new feature that has been introduced in Strategy version 9.3.1. Refer to the following Strategy Knowledge Base document for more details.

KB43532: New Feature in Intelligence Server 9.3.1: Mobile Client Statistics (iOS only)

To support this new feature in 9.3.1, 2 new lookup tables and 1 fact table (view) have been added to the Strategy Enterprise Manager warehouse:

CT_EXEC_TYPE
CT_MANIP_TYPE
CT_EXEC_FACT (view)

Each tables' function is as follows:

Custom test obsolete in ScanMD 9.000.001, included in the common tests
36276531451, 40605Check Invalid CurrentElementStatus in Reports and TemplatesApplicationThis function checks whether the page-by axis contains any unit with CurrentElementStatus as "Chosen". The fix will change the CurrentElementStatus from "Chosen" to "Desired".Current for 9.x368226 200860Check Invalid Schema Reference in XDA ReportsApplicationUnable to run reports; error of type "Object with ID 'XXX' and type 22 (Schema) is not found in metadata. It may have been deleted." occurs. This error appears while executing a FFSQL report. The test will find out all FFSQL reports (with full path) whose source tables contain invalid references to missing schema objects. This test provides no fix but necessary information and let customers be able to tell which FFSQL Reports are not working before the end users realize it.
Current for 9.x373433 31538Check SourceOrder columns corresponding to MDX SchemasSchemaAfter Project Duplication or Object Manager move
of MDX source related objects, the Source Order attribute form always
returns -1, so that it is impossible to sort/arrange the results.
This test will scan the MD for MDX-source related SourceOrder column objects
and will restore invalid properties of these columns from other information
such that the Source Order attribute forms functionality is restored.
(No access to the MDX source is needed for this operation.)Current for 9.x374107 N/ACheck Invalid Reference to Missing Metric in ReportApplicationThis test checks whether the report contains invalid reference to missing metrics in the PropertyTarget folder at both report level and template level. The fix will remove the invalid references.Current for 9.x382996N/ACheck Empty Dimty in XDA MetricApplicationThis test is to search XDA metrics with empty dimensionality and then put them in report level dimensionality. Current for 9.x38819433587, 34592Check DBRoles in DSSTable and DSSDBTableSchemaThis test provides ability to clear a DSSTable's Primary and Secondary DBRoles making a table point to the projefct's default database instanceCurrent for 9.x40061734622, 34663, 40522Check Deep Expression in ConsolidationApplicationThis test checks all consolidation elements for expressions with more than 200 pairs of nested parentheses. The fix will simplify such expressions by removing those parentheses that are not required to maintain the same order of precedence of the operators in the expression.Current for 9.x413387N/ACheck invalid prompt references in filtersApplicationThis test provides ability to remove invalid Prompt references in: embedded Filters in Reports, standalone Filters and Custom Groups.Current for 9.x431850N/ACheck invalid names of the reports and filters and their embedded objectsApplicationThis test checks whether 4 kinds of invalid characters [ ] " \ exist in the object names of Reports and Filters, as well as their embedded Filters, Prompts, and Metrics. The fix will replace invalid characters [ ] " \ with _ _ ' / respectively.Current for 9.x456977N/A Check Non-Default Web Preference Property ValuesConfigurationThis test inspects link items used to store Strategy Web User Preferences and if any of them is using a non-default value the fix will modify them to use the default value. This test is useful when the following error is observed while logging in from Strategy Web: "String index out of range: 129".Current for 9.x477180N/ACheck invalid custom group references in filters and templatesApplicationThis fix provides the ability to remove invalid Custom Group references from concrete element nodes in Filters in Report, Document, Filter, Prompt and Metric. Added fix to remove invalid Custom Group reference from concrete and subtotal element nodes in Template.Current for 9.x500807N/AInvalid Name ConversionApplicationThis test scans all Reports and Filters and the embedded Filter, Prompt, Metric objects inside them to check invalid characters like [, ], ", \. And the fix will replace those character with (, ), ', / respectively.Current for 9.x733251N/AN/AApplicationThis test scans all Reports and Filters and the embedded Filter, Prompt, Metric objects inside them to check duplicated embedded IDs in different standalone objects and the fix will change the duplicated ID to a unique one.Current for 9.x792455N/ARemove Dormant Prompt Instances from ReportsApplicationThis test scans all Reports to remove any dormant prompt instances. This will prevent the prompt instances from re-occurring when re-prompting. Current for 9.x863773N/ACheck for Invalid Visible PropertyApplicationThis test scans the visible property of panel node and its default formatting in all documents and it will reset the incorrect value for default format and exisitng panel node. Current for 9.x
State ValueLocked?0Not Locked7Locked
ArgumentDescriptionevt20003 - setPageByElement Specifies the attribute element (s) that should be selected in the page-by axis.srcSpecifies both the page component to handle the action and the event. (i.e. report.frame.rb).reportIDSpecifies the ID of the report to execute.reportNameCan be used instead of reportID.reportViewModeGrid (1) or Graph (2) Mode.elemKeyThe ID of the attribute to be selectedapplyNowTriggers the page-by action immediately after the request is sent to Strategy WebCT_EXEC_TYPE

Lookup table for execution type:

CT_MANIP_TYPE

DAY_ID

The view "CT_EXEC_FACT" is sourced from the following tables:

CT_DEVICE_STATS: Statistics table containing information about the mobile client and the mobile device.
CT_EXEC_STATS: Statistics table containing information about mobile report/document execution.
IS_DOCUMENT_STATS: Statistics table for Intelligence Server to record document executions.
IS_DOC_FACT: Fact table containing information about document job executions.
IS_SERVER: Lookup table that provides descriptive information about the server definitions being tracked.
IS_REP: Lookup table that provides descriptive information about the reports being tracked.
IS_DOC: Lookup table that provides descriptive information about the documents being tracked.
IS_PROJ: Lookup table that provides descriptive information about the projects being tracked.
EM_MD
EM_USER

The view structure is as follows:

DAY_ID	Day when the action was started. HOUR_ID
Day when the action was started. HOUR_ID	Hour when the action was started. MINUTE_ID
Hour when the action was started. MINUTE_ID	Minute when the action was started. EM_RECORD_TS
Minute when the action was started. EM_RECORD_TS	Date and time when this information was loaded into the Enterprise Manager warehouse. CT_DEVICE_INST_ID
Date and time when this information was loaded into the Enterprise Manager warehouse. CT_DEVICE_INST_ID	Unique Installation ID of the mobile app CT_STATE_COUNTER
Unique Installation ID of the mobile app CT_STATE_COUNTER	An integer value that increments whenever the device information, such as DEVICETYPE, OS, OSVER, or APPVER (in CT_DEVICE_STATS), changes. CT_STATE_CHANGE_TS
DEVICETYPE, OS, OSVER, or APPVER (in CT_DEVICE_STATS), changes. CT_STATE_CHANGE_TS	Date and time when STATECOUNTER is incremented. CT_DEVICE_TYPE
Date and time when STATECOUNTER is incremented. CT_DEVICE_TYPE	Type of device the app is installed on, such as IPAD2, DROID, or IPHONE4S. CT_OS
Type of device the app is installed on, such as IPAD2, DROID, or IPHONE4S. CT_OS	Operating system the app is installed on, such as IOS or ANDROID. CT_OS_VER
Operating system the app is installed on, such as IOS or ANDROID. CT_OS_VER	Version of the operating system, such as 5.2.1. CT_APP_VER
Version of the operating system, such as 5.2.1. CT_APP_VER	Version of the Strategy app. EM_USER_ID
Version of the Strategy app. EM_USER_ID	ID of the executing user. IS_SESSION_ID
ID of the executing user. IS_SESSION_ID	GUID of the session that executed the request. This should be the same as the SESSIONID for this request is IS_REP_FACT CT_SESSION_ID
GUID of the session that executed the request. This should be the same as the SESSIONID for this request is IS_REP_FACT CT_SESSION_ID	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:
GUID of the Strategy Mobile client session ID. A new client session ID is generated every time a user logs in to the mobile app. IS_MESSAGE_IDID corresponding to the JOBID (in IS_REP_FACT) of the message generated by the execution.CT_ACTION_IDSimilar to JOBID but generated by the client and cannot be null. (JOBID might be null if user is offline during execution.)IS_SERVER_IDGUID of the Intelligence Server processing the request.EM_APP_SRV_MACHINEName and port number of the Intelligence Server machine where the mobile document execution is taking place.IS_REP_IDGUID of the report used in the request.IS_DOC_IDGUID of the document used in the request.IS_PROJ_IDGUID of the project.IS_REPOSITORY_IDGUID of the metadata repository.EM_MOB_SRV_MACHINEName and port number of the Mobile Server machine where the mobile document execution is taking place.CT_REQ_TSTime when the user submits a request to the mobile app.IS_DOC_REQ_TSTime when the document is requested from Intelligence Server.IS_DOC_EXEC_REQ_TSTimestamp of the execution request; request time of the original execution request if a cache was hit, otherwise current session’s request time.IS_DOC_EXEC_TM_MSDifference in milliseconds between IS_DOC_EXEC_ST_TS and IS_DOC_EXEC_FN_TS.IS_DOC_QU_TM_MSQueue duration in milliseconds..CT_REC_TSTime when the mobile app begins receiving data from Strategy Mobile Server.CT_REQ_REC_TM_MSDifference in milliseconds between CT_REQ_TS and CT_REC_TS.CT_RENDER_ST_TSTime when the mobile app begins rendering.CT_RENDER_FN_TSTime when the mobile app finishes rendering.CT_RENDER_TM_MSDifference in milliseconds between CT_RENDER_ST_TS and CT_RENDER_FN_TSCT_EXEC_TYPE_IND_IDType of report/document execution:	CT_CACHE_HIT_IND_IDWhether a cache was hit during the execution, and if so, what type of cache hit occurred:
CT_CACHE_HIT_IND_IDWhether a cache was hit during the execution, and if so, what type of cache hit occurred:	.CT_PROMPT_IND_IDWhether the report or document is prompted:
.CT_PROMPT_IND_IDWhether the report or document is prompted:	CT_DATATYPE_IDWhether the job is for a report or a document:
CT_DATATYPE_IDWhether the job is for a report or a document:	CT_NETWORK_TYPEThe type of network used:
CT_NETWORK_TYPEThe type of network used:	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.
CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.	CT_BANDWIDTH_KBPSEstimated network bandwidth, in kbps..CT_VIEW_FN_TSTime at which the user either clicks on another report/document, or backgrounds the mobile app.CT_VIEW_TM_MSDifference in milliseconds between CT_RENDER_FN_TS and CT_VIEW_FN_TS.CT_NU_OF_MANIPAn integer value that increases with every manipulation the user makes after the report/document is rendered, excluding those that require fetching more data from Intelligence Server and/or result in another report/document execution.CT_AVG_MANIP_RENDER_TM_MSAverage rendering time for each manipulation.CT_LATITUDELatitude of the user.CT_LONGITUDELongitude of the user.

Further information to these tables can be found in the System Administrator Supplemental Guide > Chapter 6 (Enterprise Manager data warehouse tables)

Comment

0 comments

Details

Knowledge Article

Published:

June 5, 2017

Last Updated:

June 5, 2017