Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Appsplus panel macro confluence macro
data{"features":["title","icon","rounded","collapsible","border"],"title":"General Guidelines. **Delete before publishing**","titleColor":"#000000","titleColorBG":"#ff5c30","titleSize":"14","titleBold":true,"titleItalic":false,"titleUnderline":false,"lozenge":"Hot stuff","lozengeColor":"#172B4D","lozengeColorBG":"#fff0b3","height":200,"panelPadding":12,"panelColor":"#172B4D","panelColorBG":"#FFFFFF","borderColor":"#ff5c30","borderRadius":3,"borderStyle":"solid","borderWidth":1,"icon":"editor/info","iconPrimary":"#FFFFFF","iconSecondary":"#0052CC","newMacro":false}

**Delete Before Publishing**

  • Always use title casing for Heading formats 1 and 2.

  • Always use active voice.

  • Do not use "Please" anywhere in the document.

  • Screenshots

    • Always use the New Form UI.

    • Be optically similar. Max size corresponding gridline to 1000 px size, as in the style guide.

    • Do not capture Snap borders when showing configurations in the Examples section. You can add a border in the editor here.

    • See Image Style Guide for details.

  • Examples must always use first-person plural references. You can use the second-person if needed depending upon the example's content.

In this article

Table of Contents
minLevel1
maxLevel2
absoluteUrltrue

Overview

You can use this Snap to retrieve data objects from SuccessFactors Data Center. The Snap provides the ability to read the navigation property by expanding the navigation level. Learn more about SuccessFactors APIs: SuccessFactors Documentation.

Snap Type

The <Snap name> Snap is a Read/Write/Parse/Transform/Flow/FormatSuccessFactors Read Advanced is Read-type Snap that reads/fetches/writes/parses/executes/transforms/calls/creates…

Prerequisites

  • Valid client ID.

  • A valid account with the required permissions.

...

  • SuccessFactors Host server.

  • Valid User Id.

  • Valid Password.

Support for Ultra Pipelines

...

 

...

Works in 

...

Ultra Pipelines

Limitations

...

None.

and Known Issues

None.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

Binary

Binary or Document

  • Min: 0

  • Max: 1

  • Mapper Snap

  • Copy Snap

  • ..

  • Requires the EDI data and internal ID as a JSON document.

    Output

    Document

    Binary

    Binary or
    • CSV Parser

    • JSON Parser

    A document containing data that can be used to filter entities that need to be retrieved in SuccessFactors. 

    Output

    Document

    • Min: 1

    • Max:

    • ..

    • ..

    The EDI transaction ID and order confirmation
    • 1

    • Mapper Snap

    • Copy Snap

    • XML Formatter

    • JSON Formatter

    A document containing the data retrieved from a SuccessFactors entity.

    Error

    Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

    • Stop Pipeline Execution: Stops the current Pipeline execution if the Snap encounters an error.

    • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

    • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

    Learn more about Error handling in Pipelines.

    Snap Settings

    Appsplus panel macro confluence macro
    data{"features":["title","icon","rounded","collapsible","border"],"title":"Documenting Fields Based On Data Type/UI Element","titleColor":"#000000","titleColorBG":"#ff5c30","titleSize":"14","titleBold":true,"titleItalic":false,"titleUnderline":false,"lozenge":"Hot stuff","lozengeColor":"#172B4D","lozengeColorBG":"#fff0b3","height":200,"panelPadding":12,"panelColor":"#172B4D","panelColorBG":"#FFFFFF","borderColor":"#ff5c30","borderRadius":3,"borderStyle":"solid","borderWidth":1,"icon":"editor/info","iconPrimary":"#FFFFFF","iconSecondary":"#0052CC","newMacro":false}

    **Delete Before Publishing**

    Choose from the following sentences to document specific field types.

    Drop-down lists/Option Buttons (radio buttons):

    You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list.

    • <State what the option should do in this field>. The available options are: <bullet list of LoVs>
      Specify the Salesforce API to be used. The available options are:...

    • Select the <category> that you want to use. Available options are...
      * Option 1<italicized>. <third person singular form of the verb>
      * Option 2<italicized>. <third person singular form of the verb>
      Select the API that you want to use. Available options are:
      Bulk API. Sends the Snap execution request details as a bulk API call.
      REST API. ...
      OR
      Select one of the three following modes in which the Snap executes:
      * Validate & Execute. Performs limited execution of the Snap and generates a data preview during Pipeline validation, then performs full execution of the Snap (unlimited records) during Pipeline runtime.
      * Execute only. Performs full execution of the Snap during Pipeline execution without generating preview data.
      * Disabled. Disables the Snap and all Snaps downstream from it.

    Check boxes:

    • If selected, <Snap behavior>.
      If selected, an empty file is written when the incoming document has no data.

    • If selected, <behavior>. If not selected/Otherwise, <behavior>
      Use "If not selected" if the first sentence is long.
      If selected, the Snap uses the file path value as is. Otherwise, the Snap uses the file path value in the URL.
      If selected, an empty file is written when the incoming document has empty data. If there is no incoming document at the input view of the Snap, no file is written regardless of the value of the property.

    • Select to <action>
      Use this if the behavior is binary. Either this or that, where the converse behavior is apparent/obvious.
      Select to execute the Pipeline during validation.

    Text Fields

    • Describe what the user shall specify in this field. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc.
      Enter the name for new account.
      Specify the account ID to use to log in to the endpoint.
      Required if IAM Role is selected.
      Do not use this field if you are using batch processing.

    Numeric Text Fields

    • Describe what the field represents/contains. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc. Include special values that impact the field's behavior as a bullet list.
      The number of records in a batch.
      The number of seconds for which you want the Snap to wait between retries.
      The number of seconds for which the Snap waits between retries.
      Use the following special values:
      * 0: Disables batching.
      * 1: Includes all documents in a single request.

    Notes in field descriptions

    • Confluence’s new editor does not allow nesting of most macros inside another macro, especially the Note/Alert/Warning/Info (Panel) macros inside a table macro and Excerpt macros inside Expand or Panel Macro+ macros. So, as a workaround use the Footnotes approach as mentioned below:

      • Assign numbers at the Note locations in the form of follow through phrases like See Note 2 below this table. or such.

      • Add your Notes---an appropriate Note/Alert/Warning/Info (Panel) macro---immediately below the macro (for example, Table macro) beginning the content with the corresponding number assigned.

    Info
    • Asterisk ( * ): Indicates a mandatory field.

    • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

    • Expression icon ((blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

    • Add icon ( (blue star) ): Indicates that you can add fields in the fieldset.

    • Remove icon ( (blue star)): Indicates that you can remove fields from the fieldset.

    • Upload icon ((blue star) ): Indicates that you can upload files.

    ...

    Field Name

    ...

    Field Type

    ...

    Field Dependency

    ...

    Description

    Label*

    Default ValueELT Database Account
    ExampleELT RS Account

    ...

    String

    ...

    None.

    The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.

    Number of records

    Default Value
    Example:

    ...

    String/Expression

    ...

    Sampling Type is Number of records.

    ...

    Enter the number of records to output.

    ...

    fieldset Name

    Specify advanced parameters that you want to include in the request.

    ...

    Field 1*

    Default Value<value> or None.
    Example<value>

    ...

    String

    ...

    Debug mode check box is not selected.

    ...

    Field 2

    Default Value<value> or None.
    Example<value>

    ...

    String

    ...

    None.

    Snap Execution

    ...

    Info
    • Asterisk ( * ): Indicates a mandatory field.

    • Suggestion icon ((blue star)): Indicates a list that is dynamically populated based on the configuration.

    • Expression icon ((blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

    • Add icon ( (blue star) ): Indicates that you can add fields in the fieldset.

    • Remove icon ( (blue star)): Indicates that you can remove fields from the fieldset.

    • Upload icon ((blue star) ): Indicates that you can upload files.

    Field Name

    Field Type

    Field Dependency

    Description

    Label*

    Default Value: SuccessFactors Read Advanced
    Example: SuccessFactors Read Advanced

    String

    N/A

    Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

    Entity*


    Default Value: N/A
    Example: Foundation/Platform (PLT) – User or User

    String/Expression

    N/A

    Specify a business object from the list of business objects for SuccessFactors API. SuccessFactors stores data in multiple table structures, which are commonly known as Entities, there are various entities for Foundation as well as Personal/Employment Objects. This field will be shown dynamically from different users’ accounts from the suggestion dropdown.

    Users are allowed either to choose an entity from suggestion dropdown or type an entity manually. The entity is shown as [category name] – [entity name] in the dropdown. But it is also allowed to type only [entity name] in this field.

    Query Type


    Default Value: N/A
    Example:

    Dropdown list

    N/A

    Specify the query type. Available options include:

    • Expand

    • Custom Query

    Expand Level

    Default Value: 0
    Example: 1

    Dropdown list

    The field is only available if the Query Type is selected as Expand.

    Specify the sublevel of the business object you want to access. The business object would be expanded until the sublevel selected.

    Available options include:

    • 0

    • 1

    • 2

    Query


    Default Value: N/A
    Example:

    String

    The field is only available if the Query Type is selected as Custom Query.

    Specify the custom query. 

    Key parameter

    Use this fieldset to specify the key fields to a specific entity such as userId for the Foundation/Platform (PLT) – User entity.

    Field name

    Default Value: N/A
    Example:

    String

    N/A

    Specify the names of key Parameter (reference parameter) fields.

    Field value

    Default Value: N/A
    Example:

    Any

    N/A

    Specify the values of key Parameter (reference parameter) fields. The data type of this field depends on what Field name you selected or entered which can be String, Integer, Boolean, etc.

    URL parameters

    Use this fieldset to specify the names and values of the URL parameters.

    This fieldset is only available if the Query Type is selected as Expand.

    Parameter name

    Default Value: fromDate
    Example: fromDate

    String

    N/A

    Specify the names of the URL parameters.

    Parameter value

    Default Value: N/A
    Example: 2020-01-01

    Any

    N/A

    Specify the values for service operation fields. The data type of this field depends on what Field name you selected or entered which can be String, Integer, Boolean, etc.

    Filter records

    Use this fieldset to filter the results from the API response based on the customer-selected fields.

    The field is only available if the Query Type is selected as Expand.

    Field name

    Default Value: N/A
    Example: userId

    String/Expression/Suggestion

    N/A

    Specify the system parameter $filter fields to be included in the output.

    Operation

    Default Value:
    Example: Equals

    Dropdown list

    N/A

    Specify the comparison operator for the system parameter $filter. Available options include:

    Field value

    Default Value: N/A
    Example: test123

    String/Expression

    N/A

    Enter the values of specified input $filter fields. The data type of this field depends on what Field name you selected or entered which can be String, Integer, Boolean, etc.

    Condition

    Default Value:
    Example: Or

    Dropdown list

    N/A

    Specify the logical operator for the system parameter $filter. Available options include:

    Output field selection

    Use this fieldset to select fields to be included in the output. If not selected, all fields will be returned.

    Element

    Default Value: N/A
    Example: userId, country

    String/Expression/Suggestion

    N/A

    Specify the fields that will be displayed by descending or ascending order.

    Order by

    Use this fieldset to order the resulting records based on specified elements. The order types to be selected are either ascending or descending.

    The field is only available if the Query Type is selected as Expand.

    Order by type

    Default Value: ascending
    Example: descending

    String

    N/A

    Specify the Order Type (Ascending or Descending order).

    Output fields advanced options

    The field is only available if the Query Type is selected as Expand.

    Add advanced options to define the limited number of output entries from a specific starting entry index.

    Output entry limit


    Default Value: N/A
    Example: 10

    Integer

    N/A

    Add advanced options to define the limited number of output entries from a specific starting entry index.

    Output entry offset

    Default Value: N/A
    Example: 10

    Integer

    N/A

    This property enables you to skip the number of records the query should return.

    Automatic pagination

    Default Value: Deselected

    Checkbox

    The field is only available if the Query Type is selected as Expand.

    By default, SuccessFactors returns a maximum of 1000 records per page. If this field is selected, all matching records will be automatically returned (beyond the 1000 records).

    Note that if the field “Automatic pagination” is selected, then the field “Output entry limit” should not be set or used. Either keep the field “Output entry limit”, or check the “Automatic pagination”. In case both are used, a validation exception will be thrown.

    Allow empty query result

    Default Value: Selected

    Checkbox

    N/A

    This property enables you to determine if the empty result will be shown in the output views. If not selected, an error will be thrown when the empty result is found.

    Refresh metadata

    Default Value: Deselected

    Checkbox

    N/A

    If selected, the Snap will refresh the cache and show refreshed metadata results including new entities/parameters added or old entities/parameters deleted. This is handy in cases where changes are made to the data set outside of SnapLogic, such as a new data set created, existing data set deleted, and so on. In such cases, enabling this property will refresh the cache and display updated content. Please be aware that after the first run and new metadata has been refreshed, please de-select this checkbox.

    Pass through

    Default Value: Selected

    Checkbox

    N/A

    This property enables you to "pass through" the data from an incoming document and merge it into the new document being written to the output. If selected, the input document will be passed through to the output view under the key 'original'.

    Connection details

    Configure the connection details.

    Connection timeout*

    Default Value: 300
    Example: 100

    Integer

    N/A

    This property enables you to set the connection timeout duration of seconds

    Number of retries*

    Default Value: 3
    Example: 2

    Integer

    N/A

    This property enables you to set the maximum number of re-connections if the connection is failed or timeout.

    Retry interval (seconds)*

    Default Value: 1
    Example: 3

    Integer

    N/A

    This property enables you to set the interval in seconds between reconnections.

    Snap Execution


    Default Value: Validate & Execute
    Example: Execute Only

    Dropdown list

    N/A

    Select one of the

    following

    three modes in which the Snap executes. Available options are:

    • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

    • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

    • Disabled: Disables the Snap and all Snaps that are downstream from it.

    Troubleshooting

    Error

    Reason

    Resolution

    Account validation failed.

    The Pipeline ended before the batch could complete execution due to a connection error.

    Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.

    Examples

    Excluding Fields from the Input Data Stream

    We can exclude the unrequired fields from the input data stream by omitting them in the Input schema fieldset. This example demonstrates how we can use the <Snap Name> to achieve this result:

    <screenshot of Pipeline/Snap and description>

    ...

    You have an empty value in the Key/Value field.

    key/value parameters must not be empty.

    Please enter a valid value for key/value parameters.

    The input entity does not exist.

    An invalid entity has been entered.

    Please click the suggestion dropdown button and select the entity.

    The fields "Automatic pagination" and "Output entry limit" cannot be used at the same time.

    "Output entry limit" cannot be implemented together with "Automatic pagination".

    Please either select the "Automatic pagination" or fill the "Output entry limit" field

    Empty result found.

    There is no data coming back from the API call

    Please enable the "Allow empty query result" checkbox.

    <Entity> with key (‘<key>’) not found!

    The input key parameters entered for a specific entity is not existing in the system. 

    Please check your input key parameters and change the key parameters to existing ones. 

    Examples

    Retrieve Per Person information from the SuccessFactors data center

    This example pipeline demonstrates how to read PerPerson data via Employee Central (EC) - PerPerson API entity in the Success Factors data center. The example assumes that you have configured and authorized a valid SuccessFactors Account. T. The PerPerson entity is expanded until the second navigation level.

    ...

    Step 1: Configure the SuccessFactors Read Advanced Snapas shown below. Upon validation, the Snap displays the output showing the query results.

    SuccessFactors Read Advanced Snap Configuration

    Output

    Image Added

    Image Added

    Step 2: Connect a Mapper Snap, JSON Formatter Snap, and File Writer Snap to format and save the returned data in a new file. The configuration of the File Writer is shown below.

    ...

    Downloads

    Info
    1. Download and import the Pipeline into SnapLogic.

    2. Configure Snap accounts, as applicable.

    3. Provide Pipeline parameters, as applicable.

    Attachments
    patterns*.slp, *.zip
    sortByname

    ...

    Snap Pack History

    ...

    titleClick here to expand...
    Insert excerpt
    XYZ
    SAP SuccessFactors Snap Pack
    XYZ
    SAP SuccessFactors Snap Pack

    Related Content

    ...

    Endpoint Doc Link 1

    ...

    Endpoint Doc Link 2

    ...

    Endpoint Doc Link 3

    ...

    nameSAP_SuccessFactors_SP
    nopaneltrue

    ...

    Related Content