• Button Label:  This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}.
• Album ID: Enter the Album ID or Record ID. Leave blank to use the current Record ID. This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}.
• Component Id: Component ID to be matched by SharinPix components on the page. This is any text which will be common between this component and the SharinPix album component. It allows for matching components to communicate in case some components need to be repeated on the same record page. Example: Set 'sharinpix-1' as Target Component ID here and also on SharinPix Album component's Component ID field. This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}.
• New field API name: Text field to be used as job name. If set to None, value will default to either the record's name (if available) or the record ID. This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}.
• Auto tags: Add tags separated by the | character. These tags will be enforced on images taken by the user. This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}.
• Pdf Template Url: URL of the pdf to be filled. This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}. We use the URL on which is shared on the Pdf Template record.
• Pre-Fill Fields' API Names: Field API names of fields containing pre-filled values. The correct format is Field1|Field2|Field3. This property supports using an expression to define its custom label. The correct format is {!$Label.customLabelName}.
• Universal link: Generate a universal link when enabled instead of a deep link.

Universal links are exclusive to Apple devices running iOS, and have the ability to open a web page from an application. Instead of defining a custom URL scheme, a universal link matches a set of web pages to locations in-app. 

Deep links are a type of link that send users directly to an app instead of a website or a store. They are used to send users straight to specific in-app locations. Deep linking does this by specifying a custom URL scheme (iOS Universal Links) or an intent URL (on Android devices) that opens your app if it’s already installed.