MingLe IONAPI

fredericlebars

Hi,

I am designing a workflow.

In this workflow, I need to gain Mingle user informations from his mail address.

I tried to use Mingle API AllUsers /SocialService.Svc/User/{userGUID}/AllUsers.

Then I need to parse data from json path as this UserDetailList[?(@.Email=='%mail%')].UserName (where %mail% is dynamic)

But not possible with ion desk ionapi wf tool.

So I tried to use /SocialService.Svc/User/{userGUID}/SearchUsers but I don't understand how to fill SearchString parameter.

I did'nt see anything in docs about that subject.

 

Any Idea ?

 

Thanks for your responses Fred

Legacy Contributor

See this documentation in ION API :

-https://mingle-ionapi.inforcloudsuite.com/ICSGDENA002_TST/IONSERVICES/datalakeapi/v1/payloads/list- (M3 MT Cloud Sandbox)

This API is used to list the properties of data objects that are stored in Data Lake or have been archived.

'filter' URL parameter can be used to express "dynamic" search query by the client. It is composed of conditions, which are connected with boolean operators.

Simple condition:

(field_name operator 'value')

Conditions can be connected with "and" and "or" operators:

(dl_document_name eq '*SalesOrder') and (dl_sender_logical_id eq 'infor.jdbc.test_cp') and dl_document_date range [2017-12-19T23:24:22.410Z, 2017-12-19T23:24:22.700Z]

Conditions can be nested as follows:

(dl_document_name eq '*jdbc') and (dl_from_logical_id eq 'infor.jdbc.test_cp' OR (dl_from_logical_id eq 'infor.jdbc.test_cp' AND dl_header_accounting_entity eq "test1 c") )

Condition structure breakdown:

field_name: name of field that is going to be compared

A name of one of the attributes, belonging to the queried collection

operator: one of the binary operators for operators list below

value: Value to compare to.

If value is string, it is enclosed in single or double quotes. It is case sensitive.

double quote: value is phrase(the whole phrase is matched)

single quote: value is word. It can contain wild characters: *

If value is a number, it is not enclosed

If value is date:

If condition is 'range' : date is not enclosed and conforms to DATE_ISO8601_FORMAT = "yyyy-MM-dd'T'HH:mm:ss.SSS'Z'"; e.g. 2017-12-19T23:24:22.410Z

If condition is 'eq' : date needs to be enclosed in single or double quotes (wildcard is NOT applied)

Operator list:

eq - equals

gt - greater than

ge - greater than or equal

lt - less than

le - less than or equal

range - range of dates

Logical operator list:

and - and

or - or

Values:

Numeric values are not enclosed in quotes

Decimal numbers - dot character is used as a separator for numeric values with decimal part

Example: 123.45

Ranges:

[value1, value2] - square brackets defines inclusion of the value

Example: [1, 5] - range of values 1, 2, 3, 4, 5; both start and end values are included in the range

{value1, value2} - curly brackets defines exclusion of the value

Example: {1, 5} - range of values 2, 3, 4; both start and end values are excluded from the range

Value examples:

(dl_from_logical_id eq 'infor.jdbc.test_cp') // String, enclosed in single. Returns records where custom contains specified word. It accepts wildcard *.

(dl_from_logical_id eq "infor.jdbc.test_cp") // String, enclosed in double quotes is phrase. It returns the exact match.

(dl_from_logical_id eq "*test*") // String, enclosed in double quotes cannot contain wildcards

(size lt 35) // Number, not enclosed

dl_document_date range [2017-12-19T23:24:22.410Z, 2017-12-19T23:24:22.700Z] // both start and end timestamp are included in the result

dl_document_date range [2017-12-19T23:24:22.410Z, 2017-12-19T23:24:22.700Z} // only start timestamp is included in the result; objects having the date equal to the end timestamp are excluded

dl_document_date eq "2017-12-19T23:24:22.410Z" // Exact match date

Queryable data object properties:

dl_id - Identifier of the data object residing in the Data Lake.

event_date - Date time in which the event associated to the data object was generated. Format: yyyy-MM-dd'T'HH:mm:ss.SSS'Z'.

dl_document_date - Date time in which the data object was ingested into the Data Lake. Format: yyyy-MM-dd'T'HH:mm:ss.SSS'Z'

dl_instance_count - Number of instances in the data object.

dl_message_id - Identifier of the message that transported the data object.

dl_corrupt - A marker for corrupted data objects as determined by the Data Lake MarkCorrupt API.

dl_compression_type - Indicates the compression type applied to the data object. DEFLATE is default.

dl_encoding - Indicates the type of encoding on the raw object.

dl_document_name - Indicates the document name of the data object with direct correlation to the document name in the Infor Data Catalog.

dl_document_data_type - Indicates the data format of the data object in terms of object types supported in Data Catalog.

dl_size - Data object size in bytes.

dl_from_logical_id - Identifier of the provider of the data object.

dl_header_accounting_entity - The Accounting entity of the business object that is in the data object.

dl_header_location - The location of the business object that is in the data object.

dl_header_document_id - Document ID is the simple ID for this object in its context, for example respective accounting entity, tenant etc.

dl_header_source - Source header can be used to preserve information about message source, for example file name in case of File Connector.

dl_revision_id - Revision ID sets the value that is used to keep multiple versions of the same document unique.

dl_variation_id - The VariationID can be used at the receiving end to discover messages that are received out of sequence.

dl_batch_id - The unique ID of the batch. (ION-specific property)

dl_batch_sequence - The sequence number of this BOD in the batch. (ION-specific property)

dl_batch_size - The total number of BODs in the batch. This can be unknown until the last BOD. (ION-specific property)

dl_batch_revision - The revision number of the batch. This is used when one set of BODs fails. The complete set can be resent using a new revision number. (ION-specific property)

dl_batch_abort_indicator - This indicator type attribute is set to true when a sending system determines that it will not finish sending a batch. The receiving system is notified that any messages received as a part of this batch must be discarded. (ION-specific property)