Customer Resources Required

customer resources required for a gimmal link enterprise configuration and utility usage typically falls on the shoulders of an sap basis and/or an sap technical resource (often an sap developer who has experience in or nominated to be the document management guru configuration flows between sap archivelink (oac2, oac3) and gimmal link enterprise sap configuration, so can be handled by one resource with the appropriate authorizations in situations where gimmal link enterprise plug ins are utilized (such as more complex meta data mapping or inbound processing sap key manipulation or custom usage), working with your sap developer (if not that document admin already) will be necessary on going correspondence and collaboration will of course be required between your middleware and cms teams for configuration and testing of new patterns as new document types are configured, sap security may need to grant the necessary authorizations