View Issue Details

IDProjectCategoryView StatusLast Update
000703110000-004: ServicesSpecpublic2023-06-19 14:52
ReporterMaximilian Assigned ToMatthias Damm  
PrioritynormalSeveritytweakReproducibilityN/A
Status closedResolutionfixed 
Fixed in Version1.05.03 RC1 
Summary0007031: Ambiguous Call InputArgumentResult Codes in Part 4
Description

Call Input Argument Result Codes in Table 68 in Part 4 maybe need better description or more possible status codes related to Structures.

Thinking about custom structures which can include multiple values with different types.
In case it is not possible to decode a unknown structure by an sdk, the sdk cannot ensure that all the values are valid before executing the method on the server.
For example the sdk can´t check the type of an ExtentionObject before casting it.
In this case the method have to check the values of the structure itself after decoding.

Now the question is,

  • what StatusCode should be send if one or more of the values inside the structure are 'null'? Maybe more statuscodes are necessary.
  • and should it part of the sdk to check an ExtentionObject type or value?
TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2021-09-07 16:48

administrator   ~0014828

Agreed to clarify error handling for common call service failures. i.e. use Diagnostic fields or return "Uncertain" status and custom out parameters.

Matthias Damm

2023-06-16 15:35

developer   ~0019504

Added to Table 68 – Call Input Argument Result Codes
Bad_DecodingError
See Table 182 for the description of this result code.
Used to indicate that an input argument with a Structure DataType cannot be decoded.

Added to Table 67 – Call Operation Level Result Codes
Uncertain
The Method execution fails but the outputArguments provide additional information like an application specific error code.

But the Uncertain was already mentione in
Table 65 – Call Service Parameters
Response
results []
statusCode

Jim Luth

2023-06-19 14:52

administrator   ~0019516

Agreed to changes in Virtual F2F.

Issue History

Date Modified Username Field Change
2021-06-16 12:55 Maximilian New Issue
2021-06-17 15:35 Paul Hunkar Project Specifications => 10000-004: Services
2021-09-07 16:48 Jim Luth Note Added: 0014828
2021-09-07 16:49 Jim Luth Assigned To => Matthias Damm
2021-09-07 16:49 Jim Luth Status new => assigned
2023-06-16 15:35 Matthias Damm Status assigned => resolved
2023-06-16 15:35 Matthias Damm Resolution open => fixed
2023-06-16 15:35 Matthias Damm Note Added: 0019504
2023-06-19 14:52 Jim Luth Status resolved => closed
2023-06-19 14:52 Jim Luth Fixed in Version => 1.05.03 RC1
2023-06-19 14:52 Jim Luth Note Added: 0019516