Proposals customers that use OPERA Sales and Event Management (OSEM) from Oracle can integrate the two products so that event details entered in OSEM conveniently populate new proposals in Cendyn Proposals
- Prerequisites
- OPERA Cloud setup
- Cendyn Proposals setup
- How to test the connection?
- How does the integration work?
Prerequisites
- The Property has an OPERA Cloud Foundation license (for the connection via OHIP)
- User has screen customization permission / task granted to Opera Cloud.
Permission is: Role Manager - General - Access Options - Hub / Property Customization.
- Each property user has matching active credentials for both Oracle OSEM and Cendyn Proposals.
OPERA Cloud setup
- Log in.
- Click on the vertical ellipses on the main menu and select Settings. 
- Select option Customization - HUB / Property Level. 
- The application will reload with banner 'Customizing for XXXX', where 'XXXX' is the HUB or Hotel code.
- Go to Bookings > Blocks > Manage Block.
- Search for any existing Block and open Block Presentation Screen (e.g. by clicking on the Block ID).
- Click on the gear icon beside the Edit button. 
- Select option to Add Field > Flex Field > Add Link. 
- Type the required text label into the Text field (e.g. Cendyn Proposals).
- Click on the </> sign under Destination.
- Insert the Cendyn Proposals URL.
https://proposalaccess.com/login.aspx?hotelId=#{bindings.ResortCode.inputValue}&blockId=#{bindings.BlockId.inputValue}
- Click on Evaluate. The merged URL should show at the bottom of the Expression field. 
- Validate the hotel ID and block ID match the property and block. Click Apply.
- Leave all other screen settings on the Customize screen as they are and select Save.
- Log out of OPERA Cloud.
- This finalizes the screen customization.
Cendyn Proposals setup
- Cendyn will create an Integration User which triggers an approval request to the Customer Chain Admin. The Customer must approve the user and user role so that Cendyn can complete configuration.
- Cendyn configures the property information in the interface.
Note
If the Customer initiates the creation of the Integration User manually and links it to their organization, the user account will expire and won't function correctly. The steps above are required.
If the Customer initiates the creation of the Integration User manually and links it to their organization, the user account will expire and won't function correctly. The steps above are required.
Information required to complete Cendyn Proposals setup
- OPERA Cloud Chain code
- OPERA Cloud Property code
- OPERA Cloud version
- OPERA Cloud region
- SSD URL for the Property on OPERA Cloud
How to test the connection?
Once all configuration is complete in Cendyn Proposals and Oracle OSEM, testing can begin.
- In OSEM, open the Block Presentation screen for any block.
- Select the Cendyn Proposals button (label will be as configured).
- A new browser session opens and require the user's login credentials for Cendyn Proposals.
- The user is logged in to Cendyn Proposals and the landing page is pre-populated with all the information of the block from which the process started.
- The Cendyn Proposals button and integration is active for all users at your property.
How does the integration work?
From any block in OSEM, when a user clicks the Cendyn Proposals button, they are transferred over to Cendyn Proposals in a logged in state. All the pertinent block information is pre-populated into Cendyn Proposals so the user can quickly finish and send a proposal.
Note
The user must enter their Cendyn Proposals login credentials the first time the button is used or if they are logged out of Cendyn Proposals. Otherwise, that step is bypassed.
The user must enter their Cendyn Proposals login credentials the first time the button is used or if they are logged out of Cendyn Proposals. Otherwise, that step is bypassed.
What data is shared via the integration?
- The Arrival Date entered for a block in OSEM cannot be in the past.
- The block must have a Decision Date, which will become the Expiration Date in Proposal. If the Decision Date is in the past, the Expiration Date in Proposal will be the Event Arrival Date minus 1.
- It is recommended to always enter the primary contact’s email, and first and last name in OSEM prior to generating a proposal. If this data is missing in OSEM, the proposal will be drafted without a client. You can create a new client in Proposals, but it will not be passed back to OSEM.
- OSEM’s external Block Notes/Accommodation Notes will populate the Proposals Room Block Comments, and OSEM’s external Block Notes/Catering Notes will populate the Proposals Event Block Comments. The comments will be inserted at the time the proposal is first generated. If they are later updated in OSEM, they must be manually updated within the proposal.
- If you generate a proposal for a block but don't send it, then go back to the block and try to generate another proposal, the previously saved proposal draft will open. However, if you did send it, the next time you generate a proposal for the block, a new proposal will be created using the latest information from the booking.
- The currency code set up in Proposal will override currency codes in OSEM.
0 comments
Please sign in to leave a comment.