Corporate administrator's guide to managing multi-module orgs

For Salesforce Classic, the application menu is at the top right corner of any page.

Tip - right-click on the link and open the Delphi Select Module in a new tab. Then you can easily switch back and forth as needed.

For Salesforce Lightning, the application menu is at the top right corner of any page.

Tip - right-click on the link and open the Delphi Select Module in a new tab. Then you can easily switch back and forth as needed.

When a Delphi Select property is added to your org, the Is Delphi Select check box is selected on the Property page. This "flag" allows you to exclude Delphi Select properties from workflows and validation rules, which should be your best practice. For example, if you have a validation rule that prevents turning a booking definite when the Catering Manager field is blank, that is problematic because the Catering Manager field is not on the Booking page in Delphi Select. Here's another example - properties using Delphi Select have a pre-defined set of autotraces to remind users to complete common tasks like requesting the rooming list before the cutoff date. Many of your Delphi workflows would just be duplicates.

When Amadeus updates your org to enable multiple modules, we'll add the following qualifier to all of your workflows and validation rules: "nihrm__Location__r.nihrm__IsLimitedService__c = False" . If you create new workflows or validation rules, you'll need to manually add this qualifier.

You can copy and paste the above text, or from the workflow or validation rule, click Insert Field, select the object you're working in (booking, inquiry, volume contract, etc.), Property >, and then Is Delphi Select. Set the value to False.

To learn more about workflows and validation rules, see Salesforce Help.

Corporate setup values are shared amongst all properties—regardless of the module. When a new Delphi Select property is created, it comes with a default set of property setup values like market segments, event classifications, function room setups, etc. Those will be displayed along with your corporate values.

Before creating corporate setup values, carefully consider the impact those values will have on Delphi Select users—the goal is to avoid duplicate values.

While the setup values are shared, there are a few Delphi corporate features that do not impact Delphi Select properties:

• Corporate merge templates
• Corporate menus, items, and choice groups
• Corporate date collections
• Availability Settings - these will apply if you open the Availability page in Delphi, but do not impact the view for Delphi Select users
  

Add a new user to Delphi Select

From Delphi, click the Application menu at the top of the page and select Amadeus Delphi Select. The Delphi Select Home page will open. Click Setup, and then Users. Follow the on-screen Training & Help to create the user and add the appropriate property access.

Add a new user to Delphi

If you're creating a user that will only work in Delphi, click Setup on the Delphi Home page. See Create users.

Add a new user to multiple Modules

If you have a user who needs access to Delphi and Delphi Select properties, follow these steps:

1. Create the user in Delphi, and assign the appropriate license and profile.
   
2. Click the Permission Set Assignments related list, click Edit Assignments, and add the appropriate permission sets for each module.
   
3. In the Manage User Property Access window, assign the user access to the appropriate properties. Make sure the user's default property is a Delphi property.

For Delphi Select properties, always assign Edit All Records for Administrators.

Below are the configurations that should be applied, based on the users role.

User Access:

Users responsible for creating or managing bookings for both Delphi and Delphi Select properties should complete all of their work in Delphi only. As long as the user has access to the properties, they can do this without needing an additional Delphi Select permission set.

Property Admin Access - unable to create users:

Admin Access - with ability to create users:

Multi-Factor Authentication (MFA)

Because MFA is enabled on the user profile, you can work in either module to update your users. When you assign the Enable Multi-Factor Authentication permission set to a user in the Delphi module, if you open that same user in the Delphi Select module you'll see that it updates the Enable Multi-Factor Authentication check box. The same is true in reverse.

A default set of merge templates are provided for each Delphi Select property, including contracts, a proposal, group resume, etc.

If you have a brand standard document you would like your Delphi Select properties to use, you can share a corporate template from Delphi.

Only Advanced Booking template types can be shared with Delphi Select properties.

1. Navigate to Document Templates.
2. Either select an existing corporate template, or create a new corporate template.
3. In the Document Template Edit page, select the Share with Standard & Essentials check box.
   
   

After you save, all of your Delphi Select users will see the template when they click Print Booking.

BEOs, Banquet Checks, and Booking Checks are not supported. Delphi Select Module properties must use the default property templates for these documents in order for their revenue classifications to map correctly.

R43 or higher

If your salesforce Organization-Wide Default for Accounts is set to Public Read/Write users at all properties, regardless of module, will see and share all accounts and contacts.

When using the Private sharing model, review the Default Account Sharing option in the Admin Settings page within the Delphi Select Module. You can choose whether or not new accounts are automatically shared with all properties.

R42 or lower

While you have a choice regarding the sharing of accounts in Delphi, in Delphi Select all accounts and contacts are shared with all properties.

If your org uses the public sharing model (where all accounts are shared automatically with all properties), users at all properties, regardless of module, will see and share all accounts and contacts.

If your org uses the private sharing model:

• Accounts that are created in Delphi will only be accessible to properties that have been granted access to the account.
• All properties, regardless of module, are available to be selected when sharing the account in Delphi.
• Accounts that are created in Delphi Select are shared automatically, and all properties in all modules will have access to them.

It's a good idea to meet as a team to discuss how your organization will handle sharing and management of accounts and contacts.

To view all properties in your org, regardless of module, click the Properties tab. We recommend adding the Is Delphi Select (formerly known as Standard or Essential) field to your list view so you can easily see which module is associated with each property.

From Delphi, you can view any property's details. To edit a Delphi Select property, use the quick link at the top of the Property page to switch to the Delphi Select user experience and make your edits there.

As of R38, inclusive pricing is available for the Delphi Select module. If you enable inclusive pricing, that applies to all properties regardless of module. If you are using inclusive pricing in Delphi and you have existing Delphi Select properties, when you upgrade to R38, the inclusive pricing fields and merge templates will be displayed to them immediately after upgrade. Make sure your Delphi Select properties are ready for that change, and provide them with the list of tasks they need to take if they will use inclusive pricing. See Overview: Inclusive pricing for Delphi Select