SAP C_C4H620_34 - SAP Certified Associate - Implementation Consultant - SAP Customer Data Cloud

To add a new custom field to the accounts schema in SAP Customer Data Cloud, you can use either of the following methods:

Schema Editor in the Admin Console: This is a user-friendly interface within the admin Console where you can visually add and configure custom fields directly in the accounts schema.

Navigate to the schema editor.

Add the new custom field with the desired attributes and settings.

Save the changes to update the schema.

REST API (accounts.setSchema): This method allows for programmatic updates to the accounts schema.

Make an API call toaccounts.setSchemawith the necessary parameters to define the new custom field.

Include the field's name, type, and any other required attributes in the request payload.

Both methods provide flexibility in how you manage and extend the user schema to include additional custom fields based on your specific requirements.

References

SAP Customer Data Cloud Schema Editor Documentation

SAP Customer Data Cloud REST API Documentation

The error when calling the methodgigya.accounts.switchScreen([screenSet Default-RegistrationLogin", screen 'new-screen-id']);is due to the absence of the:

containerID parameter (C): This parameter specifies the container in which the screen should be rendered.

References

SAP Customer Data Cloud Mobile SDK Documentation

SAP Help Portal on Screen-Sets and UI Customization

To fetch a preference object from a customer in SAP Customer Data Cloud using an API, you should use:

accounts.getAccountInfo:

This API call retrieves comprehensive information about a user's account, including their preferences.

You can specify which parts of the account data you want to retrieve by using theincludeparameter to include preferences.

References

SAP Customer Data Cloud API Documentation

When a new user registers using Facebook login, the Facebook account identity will be stored in the Profile schema of SAP Customer Data Cloud. The Profile schema includes various attributes related to the user's identity and personal information.

Profile Schema:

Contains attributes such as name, email, and social media identities.

Stores the Facebook account information including the user's social identity details.

Integration: Ensures that social identities are stored and managed in a structured manner within the Profile schema.

References

SAP Customer Data Cloud Profile Schema Documentation

In SAP Customer Data Cloud, you can maintain various login identifier settings. The settings include:

A custom login identifier: This allows you to define a custom identifier for login purposes, providing flexibility in how users access the system.

A username: This is a traditional login identifier allowing users to log in using a unique username.

These settings enable customized and secure login methods, accommodating diverse authentication requirements.

References

SAP Customer Data Cloud Login Identifier Settings Documentation

In a JSON Web Token (JWT), the attribute that represents the UID of the user is:

sub (subject):

Thesubclaim is a standard claim in JWT that represents the subject of the token, which is typically the unique identifier (UID) of the user.

References

JWT Specification

To launch the Delegated Administration console for implementing CIAM for B2B on a customer's website, you need:

Endpoint:openDelegatedAdminLogin

Parameter:orgID

These are required to open the Delegate Admin function and allow access to the administration console.

References

SAP Customer Data Cloud CIAM Documentation

SAP Help Portal on Delegated Administration

To ensure that only users who have granted consent are exported to an SFTP server using dataflows, you should use thedatasource.read.gigya.accountcomponent with the consent parameter.

Using datasource.read.gigya.account with consent parameter:

This component reads account data from SAP Customer Data Cloud.

By specifying theconsentparameter, you can filter the accounts to only include those where users have given consent.

This approach ensures that only data from consenting users is included in the export.

References

SAP Customer Data Cloud Dataflows Documentation

The recommended approach to make a native API call, such asgetAccountinfo, from an Android client is to:

Use internal SDK method Gigya.getInstance().send to call the API method with an application key and secret (D): This method allows you to securely call the API using the provided application key and secret.

References

SAP Customer Data Cloud Android SDK Documentation

SAP Help Portal on Native API Calls