A media publisher is using advertising sales management to manage their b2b ad sales business using google ad manager. A consultant added a new placement on an existing media plan. When adding the new placement, the media plan remains in an inactive state in GAM. What should the consultant do to clear the inactive state after adding the new placement?
A publishing company has an existing media plan creation process that was setup using OmniStudio a few months ago. A new requirement has ome up where the user will be required to enter a new secondary budget field and this field should be stored with the rest of the media plan details. On which object should a consultant add this field so that it is stored with the rest of the media plan and can be added to the appropriate OmniScript?
When adding a new secondary budget field required for media plan creation, the consultant should add this field to the Media Plan Placements object. This object is specifically designed to store detailed information about each placement within a media plan, making it the appropriate place to store budget-related data. Adding the field here ensures that it aligns with the rest of the media plan details and can be seamlessly integrated into the corresponding OmniScript for data capture and processing. Reference: https://developer.salesforce.com/docs/atlas.en-us.omnistudio.meta/omnistudio/
A media cloud customer is already running advertising sales management (ASM) on an org and wants to upgrade from an older release. What should a consultant do before migration?
Two Salesforce Developers work for a B2B advertising publishing company. Developers A and B have been working in developer orgs with advertising sales management (ASM) and need to migrate the ASM components to the sandbox org of the company. Developer A migrates the ASM components to the sandbox org. Developer B does the same. After that, Developer A realizes that the components on the sandbox org are different from those of the developer org because they were overwritten by the components of the Developer B. There is no way to go back to recapture them. Which tool should a consultant reccomend to avoid this outcome ?
To prevent the overwriting of components during migrations and ensure consistency across development environments, a consultant should recommend using a Version Control System (B). Version control allows developers to track and manage changes to code, enabling collaboration while preserving the history of modifications. It prevents conflicts like those experienced by Developers A and B by providing mechanisms to merge changes and resolve conflicts systematically. Reference:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_intro.htm
https://help.salesforce.com/articleView?id=sf.dx_get_started.htm
Due to internal and external security compliance requiments, a customer need to mask a number of custom text fields, besides implementing Field Level Security. These field values have less than 100 characters in length. However, a select group of users are allowed to view these field values as a part of their daily work. How should a consultant implements this?
To mask custom text fields while meeting security compliance requirements and allowing select users to view the field values, a consultant should implement Salesforce Shield Platform Encryption (B) and configure profiles accordingly. Shield Platform Encryption provides a higher level of data protection by encrypting sensitive data at rest without compromising application functionality. By configuring profiles, the consultant can specify which users or groups have the permission to view the decrypted field values, ensuring compliance with both internal and external security mandates. Reference:
https://help.salesforce.com/articleView?id=sf.security_pe_overview.htm
https://help.salesforce.com/articleView?id=sf.pe_profiles_perm_sets.htm
Francesco
2 days agoSage
1 months agoVerona
2 months agoAlishia
3 months agoCordelia
3 months agoFelix
4 months agoIsidra
4 months agoJosephine
4 months agoHalina
5 months agoLashawnda
5 months agoAndree
5 months agoStefanie
6 months agoFrancoise
6 months agoTerina
6 months agoLinsey
7 months agoMaira
7 months agoSue
7 months agoCherilyn
7 months agoCharlette
8 months agoDenae
9 months agoJaney
10 months agoDominga
10 months agoKiera
10 months agoEllen
10 months agoLottie
10 months agoLing
10 months agoRonnie
11 months ago