Viewing and Attachment List Options

viewing content is accomplished via two access points from your sap transaction / record direct to your content repository (optional) from sap viewing from sap is achieved via the sap or gimmal link enterprise docmanager attachment list (object for services) accessing content from these attachment lists perform the following authorization checks access to your sap transaction / record with standard sap authorizations access to the archivelink with standard sap authorizations optional additional sap badi authorization checks optional additional sap gimmal link badi authorization checks from there, gimmal link provides 2 options to retrieve and display the content from your cms system for url based viewing 1\ user un authenticated access (authenticated by link enterprise app) the method leveraged to achieve this differs based on your cms system m365 anonymous short lived shared urls via web browser gimmal link content server via a non dialogue system user (thin and thick client options) aka standard sap viewing s3 1\ gimmal link archive link content server url 2\ user authenticated access via sharepoint whilst still leveraging sap standard archivelink and dms links, gimmal link enterprise can compile a viewing url directing the user to log into the sharepoint system view their web browser this option leverages any security capabilities and options based on your cms system these are in addition to the check outlined in "from sap" refer to the section " cms security based on sap security / data " below for possible additional security checks based on sap values please refer to your cms systems' security documentation for further options comparing viewing options viewing option all repositories pros cons additional tasks user unauthenticated content server archivelink no additional sharepoint config needed no additional sharepoint user setup not all mime types supported replies on local workstation web browser or sap viewer and workstation apps to handle viewing no sharepoint authentication caches a local copy on user's workstation binary sent across wire actually performs a search on sapdocid as metadata to find document, thus performance may be affected at high volumes none sharepoint user unauthenticated anonymous sharepoint url supports all m365 online supported mime types no binary sent across wire no local workstation browser or application requirements no local workstation caching no search necessary, thus no performance considerations (direct read) less sharepoint maintenance bypasses user level access to site/subsite/library authorizations (link enterprise app/user is used) when viewing from sap, user does not have to log on to m365/sharepoint requires sharepoint anonymous viewing enabled at tenant level or site collection level (i e these are short lived url's that in theory can be copy/pasted and shared to other users before expiration (default 1 minute) refer to the below https //learn microsoft com/en us/microsoft 365/solutions/best practices anonymous sharing?view=o365 worldwide https //learn microsoft com/en us/microsoft 365/solutions/best practices anonymous sharing?view=o365 worldwide sharepoint tenant level config user authenticated sharepoint url more authentication and security more sharepoint maintenance users must have access to that site/subsite/library when viewing from sap, the user will need to log on to m365/sharepoint if/when their active m365/sharepoint session expires or is logged out (frequency is based on customer setup) does not require sharepoint anonymous viewing enabled at tenant / site collection level sharepoint user/group maintenance required sap sfo/gos attachment list options you can leverage the standard sap attachment list or (highly recommended) the gimmal link enterprise docmanager attachment list refer to the section "attachment list options" under the docmanager section for advantages in using the gimmal link enterprise docmanager attachment list plus additional sfo/gos configuration options with gimmal l ink enterprise direct to your cms system allowing access to content directly via your cms system relies solely on that systems' security model and capabilities refer to the section " cms security based on sap security / data " below for possible additional security checks based on sap values please refer to your cms systems' security documentation for further options cms security based on sap security / data gimmal link enterprise does not replicate the sap security model to your cms system if, however, your cms system can leverage sap data in the form of metadata or cvl's (choice lists), you can leverage gimmal link enterprise sap to inform your cms system with those values (i e metadata transfer)