Audience: build-along attendees (customer-facing). Copperline Equipment Finance, its people and its customers are fictional, made up for the AppExchange Amplified build-along.
You have built the five requirements from Copperline's business case, on the fields and records from the Build page. The Talent Show asks for one more: a sixth requirement of your own, built on top of what you have, in the same org. Pick one of Copperline's problems below, or bring your own.
Two weeks after go-live, Rachel and James came back with a list. Each is something Copperline still does by hand, or a gap the first five requirements left open. There are two for each CloudFiles product.
How you solve it is up to you. Each one comes with a hint: the CloudFiles capability that could help, and the help articles to start from. Treat the hints as a starting point, not the answer.
1. Files attached in Salesforce end up in the right folder too Not everyone uses the CloudFiles widget. Some of the team still drag documents into the Files list on the Opportunity, and emails logged to the deal bring their attachments into Salesforce Files. Those documents never reach the deal folder, so they are not sorted, nobody can find them later, and they fill up Salesforce file storage, which Rachel asked to avoid on day one. Done looks like: any file attached to an Opportunity in Salesforce is copied into that deal's folder, where your existing sorting files it into the right subfolder like any other upload. Once the copy has safely landed, the Salesforce copy is removed. Hint: CloudFiles raises an event when a file is attached to a record in Salesforce, can copy Salesforce Files into a connected folder, and raises a second event when the copy is done. Remove the original only after that second event, never before.
2. A dataroom for the supplier Before paying a supplier, Copperline sends them the deal paperwork and the delivery details. Today that is a long email with attachments, which gets forwarded, can never be taken back, and leaves no record of who opened what. For bigger deals the supplier's finance team asks for the same pack again a week later. Done looks like: from the Opportunity, the deal owner creates a dataroom for the supplier with a chosen set of the deal's documents, such as the application form, the supplier invoice and the agreement, and shares it through one secure link that can expire. The dataroom is visible from the record. Hint: look at Datarooms, which group chosen files behind one link, and the link settings that control expiry and passwords. Both can be created from a flow.
3. Read the driving licence too The invoice is now read automatically, but the driving licence is not. Someone still opens every licence and types the holder's name, licence number and expiry date into Salesforce. Twice last quarter a deal went through on a licence that had already expired, because nobody looked at the date. Done looks like: when a driving licence is filed into Identity, its name, licence number and expiry date land on the deal, and a licence that has expired is clearly flagged on the Opportunity. Hint: this is the same pattern you used for the supplier invoice, pointed at a different document. Set up a new Document Mapper configuration for the licence, mapping each value to a field on the Opportunity, and test it right there in the mapper against a sample licence before you wire it into your flow.
4. One scan, five documents Some borrowers do not send separate files. They feed everything into the office scanner and send one 12-page PDF with the application form, the invoice, the licence and the utility bill all in it. The sorting you built cannot file it, because it is not one document. Someone splits it by hand before anything else can happen. Done looks like: a combined PDF dropped into the deal folder is split into its separate documents, and each one is filed into the right subfolder, just as if the borrower had sent them separately. Hint: look at AI document splitting, which breaks one file into its parts and tells you when it is done, so your existing sorting can take over.