Difference between revisions of "Extensions.DateTime.GetTimeStamp"
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
{| {{TableHeader}} | {| {{TableHeader}} | ||
{{TableRowPropertiesHeader}} | {{TableRowPropertiesHeader}} | ||
− | {{TableRowPropertie1| Result | [[Integer]] | [[Value]] | - | [0..1] | This result eturns a timestamp in milliseconds }} | + | {{TableRowPropertie1| Result | [[Integer]] | [[Value]] | - | [0..1] | This result eturns a timestamp in milliseconds This option tells the communication backend to make this diagnostic service execution non-blocking. This means that if executeAsync is set to true, the OTX execution flow will immediately move on to the next Action, without waiting for the result of the ExecuteDiagService action.}} |
|} | |} | ||
Revision as of 11:42, 11 July 2014
Classification
Name | GetTimeStamp |
Short Description | Returns a formatted time representation of a timestamp |
Class | Term |
Extension | OTX DateTime Extension |
Group | - |
Exceptions | - |
Checker Rules | - |
Standard Compliant | Yes |
Pseudo-Code Syntax
timeStamp = GetTimeStamp();
Description
GetTimestamp shall return a timestamp, expressed in milliseconds elapsed since 1970-01-01 00:00:00 UTC.
Properties
Name | Data Type | Class | Default | Cardinality | Description |
Result | Integer | Value | - | [0..1] | This result eturns a timestamp in milliseconds This option tells the communication backend to make this diagnostic service execution non-blocking. This means that if executeAsync is set to true, the OTX execution flow will immediately move on to the next Action, without waiting for the result of the ExecuteDiagService action. |