| Salesforce SME, Remote at Remote, Remote, USA |
| Email: [email protected] |
| From: Yogesh Sharma, StellentIT [email protected] Reply to: [email protected] Salesforce SME Remote Phone + Skype Job description: The North Carolina Department of Commerce is requesting services from a Salesforce Administrator/Developer to provide an analysis of the Salesforce solution consisting of a single Salesforce Org for two separate and distinct divisions, the Division of Workforce Solutions (DWS) and the Rural Economic Development Division (REDD), referred to as the business units. Each division manages its own users, applications, processes, and forms to meet their separate business needs with little overlap or sharing of data. The data and applications are split within the Org using public read/write permissions. The selected Administrator/Developer will: Determine the feasibility, cost, and timeframe to separate the divisions into two separate Salesforce Orgs. Assess the REDD Division solution to determine whether the underlying system design and configuration should be used going forward in a new, single-tenant Org. Brief History In 2020, DWS hired a Salesforce vendor to develop and implement an Online CRM to help log and manage North Carolina company information used for reporting to the Department of Labor. Later in 2021, DWS extended their CRM to include a grants management application. In 2022, the REDD Division hired the same Salesforce vendor to develop their own grants management CRM, which was also deployed in the same Org with DWS. The CRM permits governmental units across the State to submit requests for grants and services through a public facing portal. REDD Division staff use the CRM to manage the funding requests and ensure grant requirements are met. The decision to deploy the REDD Division solution in the same Org was based on an urgent need to distribute emergency grant funding, which would have resulted in delay without an existing Org in production, and the potential to share common information with DWS. However, several challenges were soon identified such as limitations in the naming of Salesforce objects and fields, limited use of sandbox environments, and the erroneous appearance of data fields created for one business solution appearing in the other. It was also later determined that the potential to share common information would not be feasible. As such, the REDD Division sought the assistance from Salesforce specialists who were able to guide the business units through a high-level Org health assessment to determine whether the business units were suited to share the same Org. The following justifications were identified to separate the business units into two separate Orgs. 1. The business units have different overall goals. 2. Business processes are different enough to require custom processes. 3. The business units maintain separate accounts and customer profiles. 4. Reporting is separate. 5. The business units will continue developing their solutions at different times. REDD Division Solution Issues In addition to the challenges of sharing an Org, the REDD Division solution has system issues that impact daily performance or prevent additional customizations needed for key business processes. Current solution issues are: 1. Scalability a. The solution was deployed for the management of 4 grant programs with most workflows and processes identical between one another. Similar grant programs cannot be added without significant, costly development. b. The solution must be able to send and receive e-mail communication from each subrecipient agreement, which is the main repository for the functions of an awarded grant. Currently, the solution permits an internal user to send an e-mail from the Subrecipient agreement, but the response e-mail only goes to the senders Outlook email inbox. It is required that the return email response must also automatically be delivered to the correct subrecipient record in Salesforce. The current solution cannot support this 2-way communication in its current cloud type. 2. Data Management a. Ineffective Private Read/Write permissions fail to prevent REDD Division applicants from selecting DWS data during application completion. b. The solution fails to prevent the duplication of accounts and contacts. 3. Environments Management a. Unexpected differences occur between the development sandbox and production environments. b. No Versioning History. 4. Queue and Permissions Management Approval queues appear to be inconsistent across automated processes. Groups and queues established by the vendor do not appear to be reconfigurable without additional development. Potential factors which may be contributing to the current solution issues are: 1. Current cloud type is not conducive to scala Keywords: information technology |
| [email protected] View all |
| Tue Oct 10 00:36:00 UTC 2023 |