AppXtender (CMIS Binding) - Revision history

Dsmith: /* Submitting an Import Job with AppXtender */

2025-05-29T18:30:08Z

Submitting an Import Job with AppXtender

← Older revision		Revision as of 13:30, 29 May 2025
Line 86:		Line 86:
	# Click the Imports icon.		# Click the Imports icon.
	# Click the Add New Jobs button.		# Click the Add New Jobs button.
	#		#: <li class="fyi-bullet"> IMPORTANT: You will need to have an Import Watcher service installed and running prior to submitting an Import Job </li>
	#		# Add a Description.
	#		# Choose an Import Provider, generally either Import Descendants or Import Query Results.
	#		# Click through the Node Type Objects until locating the App Enhancer Repository, and select it.
	#		#* If you have chosen Import Query Results, you will need to refine your import by configuring a CMIS Query.
	#		#* For Import Descendants, no refinement is necessary unless you do not wish to pull from the root level of the Repository.
			# If you wish to process the Batch upon import, configure the Batch Creation propery; otherwise, click Submit.
			# Grooper will display the details of your Import Job within the list window.
			# Once the job is complete, you can view the imported Batch by going to the Design page, then ''Batches --> Test --> Imported Batches'' and then selecting your Batch.
			#* Note, that Grooper automatically names the Batch after the date and time the import job was submitted.
			#* If you processed the Batch upon importing, it will be within the Productions Folder.

	=== Exporting ===		=== Exporting ===

Dsmith: /* Configuring an Export Behavior */

2025-05-29T18:20:24Z

Configuring an Export Behavior

← Older revision		Revision as of 13:20, 29 May 2025
Line 100:		Line 100:
	# Select the Export Definitions property and click <code> "..." </code> to open up the Export Definitions Editor window.		# Select the Export Definitions property and click <code> "..." </code> to open up the Export Definitions Editor window.
	# Click the Add button and select CMIS Export from the dropdownlist.		# Click the Add button and select CMIS Export from the dropdownlist.
	#		# To choose the Repository you will be exporting your Batch contents to, click <code> "☰" </code> to open the dropdown list.
	#		# Click through the Node Objects until finding the AppEnhancer Repository and select it.
	#		# If you have a specific folder within the Repository where you wish to export the Batch contents, define it with the Target Folder property by clicking <code> "..." </code> and choosing the desired folder within the selection window.
	#		#* If you wish to export your Batch contents to the root folder, leave the Target Folder property unconfigured.
			# Choose the Object Type.
			# Configure Read Mappings and/or Write Mappings if necessary.
			# Click OK when finished.
			# Click OK on the Behaviors window.
			# Save changes.

	== Earlier Versions of ApplicationXtentder and End of Life Support Schedule ==		== Earlier Versions of ApplicationXtentder and End of Life Support Schedule ==

Dsmith: /* Configuring an Export Behavior */

2025-05-29T18:16:11Z

Configuring an Export Behavior

← Older revision		Revision as of 13:16, 29 May 2025
Line 95:		Line 95:
	=== Exporting ===		=== Exporting ===
	==== Configuring an Export Behavior ====		==== Configuring an Export Behavior ====
			# Select the Content Type Node Object where you wish to configure the Export Behavior.
			# Select the Behaviors property and click <code> "..." </code> to open the Behaviors Editor window.
			# Click the Add button and select Export Behavior from the dropdown list.
			# Select the Export Definitions property and click <code> "..." </code> to open up the Export Definitions Editor window.
			# Click the Add button and select CMIS Export from the dropdownlist.
			#
			#
			#
			#

	== Earlier Versions of ApplicationXtentder and End of Life Support Schedule ==		== Earlier Versions of ApplicationXtentder and End of Life Support Schedule ==

Dsmith: /* Submitting an Import Job with AppXtender */

2025-05-29T18:09:54Z

Submitting an Import Job with AppXtender

← Older revision		Revision as of 13:09, 29 May 2025
Line 84:		Line 84:

	==== Submitting an Import Job with AppXtender ====		==== Submitting an Import Job with AppXtender ====
			# Click the Imports icon.
			# Click the Add New Jobs button.
			#
			#
			#
			#
			#
			#

	=== Exporting ===		=== Exporting ===

Dsmith: /* Configuring an Import Behavior */

2025-05-29T18:03:27Z

Configuring an Import Behavior

← Older revision		Revision as of 13:03, 29 May 2025
Line 75:		Line 75:
	# Select the Import Definitions property and click <code> "..." </code> to open the Import Definitions Editor window.		# Select the Import Definitions property and click <code> "..." </code> to open the Import Definitions Editor window.
	# Click the Add button and select CMIS Import from the dropdown list.		# Click the Add button and select CMIS Import from the dropdown list.
	#		# Select the CMIS Repository property and click <code> "☰" </code> to access the dropdown list and select the Repository where Grooper will import/map data.
	#		# Choose the AppEnhancer Repository.
			# Choose the Content Type.
			# Configure Read Mappings and Write Mappings if necessary.
			# Click OK when finished.
			# Click OK in the Behaviors Editor window.
			# Save changes.

	==== Submitting an Import Job with AppXtender ====		==== Submitting an Import Job with AppXtender ====

Dsmith: /* Configuring an Import Behavior */

2025-05-29T17:58:49Z

Configuring an Import Behavior

← Older revision		Revision as of 12:58, 29 May 2025
Line 70:		Line 70:
	=== Importing ===		=== Importing ===
	==== Configuring an Import Behavior ====		==== Configuring an Import Behavior ====
			# Select the Content Type Node Object (Content Model, Document Type, Content Category) where you want to configure the Import Behavior.
			# Select the Behaviors property and click <code> "..." </code> to open the Behaviors Editor window.
			# Click the Add button and select Import Behavior from the dropdown list.
			# Select the Import Definitions property and click <code> "..." </code> to open the Import Definitions Editor window.
			# Click the Add button and select CMIS Import from the dropdown list.
			#
			#

	==== Submitting an Import Job with AppXtender ====		==== Submitting an Import Job with AppXtender ====

Dsmith: /* Importing and Exporting with AppXtender */

2025-05-29T17:39:39Z

Importing and Exporting with AppXtender

← Older revision		Revision as of 12:39, 29 May 2025
Line 69:		Line 69:
	== Importing and Exporting with AppXtender ==		== Importing and Exporting with AppXtender ==
	=== Importing ===		=== Importing ===
			==== Configuring an Import Behavior ====
	==== Submitting an Import Job with AppXtender ====		==== Submitting an Import Job with AppXtender ====

Dgreenwood: /* How to create an AppEnhancer connection */

2025-05-19T20:34:20Z

How to create an AppEnhancer connection

← Older revision		Revision as of 15:34, 19 May 2025
Line 32:		Line 32:
	[https://app.supademo.com/demo/cm9t0r61e0ex811m7z65vf30b?step=1 Click here for an interactive walkthrough]		[https://app.supademo.com/demo/cm9t0r61e0ex811m7z65vf30b?step=1 Click here for an interactive walkthrough]

	# Right-click the ~~'''Project'''~~ (or ~~'''Folder''') where you want to add your '''CMIS Connection'''~~.		<big>Create a CMIS Connection</big>
	# Select "Add", ~~followed by~~ "CMIS Connection..."		# Right-click a Project in the node tree (or a folder in the Project.
	# ~~Name your '''~~CMIS Connection~~''' and click~~ "Execute".		# Select "Add", then "CMIS Connection..."
	~~# Within your new '''~~CMIS Connection~~''', select~~ the ~~'''''~~Connection Settings~~''''' property and expand the~~ dropdown ~~menu~~.		# Enter a name for the CMIS Connection.
	# ~~Choose '''''~~AppXtender~~'''''~~.		# Select "Execute".
	# ~~Having selected your '''''Connection Type''''', expose the sub-~~properties ~~and enter~~ in ~~the following information:~~
	#* '''''Web Services URL~~'''''~~		<big>Configure the CMIS Connection for AppEnhancer (formerly ApplicationXtender)</big>
	#* '~~''''~~Data Source Name~~'''''~~
	#* ~~'''''Username'''''~~		#<li value=5> Use the "Connection Settings" dropdown editor to select "AppXtender".
	#* '''~~''Password''~~'''		#* The "AppXtender" binding defines settings for Grooper to connect to AppEnhancer.
	# ~~Save~~ and ~~click~~ the List Repositories button to ~~display available '''~~Repositories~~''' within your AppXtender service~~.		#* The AppXtender binding has several configurable properties. We will detail those that are required to connect to AppEnhnacer data sources in this tutorial.
	# Select the ~~'''Repository'''~~ you ~~want~~.		# Configure the "AX Web Services URL" property.
	# ~~Click~~ the Import ~~Repositories~~ button, ~~then~~ Execute.		#: Enter your AppEnhancer web services (formerly "AX web services") URL. See below for the most common URL formats.
	# ~~Once successfully imported, your Repository~~ will ~~appear as~~ a ~~child~~ '''~~Object''' of your~~ '''CMIS Connection~~'''~~.		#:* For AppEnhancer: <code><nowiki>https://{{host_name}}/AppEnhancerServices/AxServicesInterface.asmx</nowiki></code>
			# Enter your AppEnhancer data source's name into "Data Source Name".
			#:*<li class="fyi-bullet"> The AppEnhancer data source is the parent repository for AppEnhancer applications.
			# Enter the username and password for the AppEnhancer user into the "User Name" and "Password" properties.
			# Save the CMIS Connection.

			<big>Import an AppEnhancer CMIS Repository</big>

			Having saved your connection settings, Grooper has established a connection to your AppEnhancer data source, and you can now import applications in AppEnhancer as storage locations in Grooper. This will create a '''CMIS Repository''' node Grooper can use to interact with files an an AppEnhancer application. To do so:
			# <li value="8">Select the CMIS Connection and press the "List Repositories" button.
			#*<li class="fyi-bullet">"CMIS Repositories" and "CMIS Connections" are two different things in Grooper.
			#:* CMIS Connections only connect Grooper to AppEnhancer.
			#:* CMIS Repositories represent the files in an AppEnhancer application.
			# The "List Repositories" button lists available AppEnhancer applications that can be imported into Grooper as CMIS Repositories. Select the application you wish to import.
			#*<li class="fyi-bullet> At this time, the value under "Imported" will be "False", and the dot next to it will be red. Once imported, this value will change to "True", and the dot will turn green.
			# Press the "Import Repository" button to import the application into Grooper.
			# In the pop-up window, ensure the listed repository is the one you wish import, and press the "Execute" button.
			# This will add a '''CMIS Repository''' node to the CMIS Connection (as its child).
			# Grooper will use this CMIS Repository node when importing files from or exporting Grooper documents to AppEnhancer applications.
			#* The CMIS Connection only initiates the connection from Grooper to an AppEnhancer data source.
			#* The CMIS Repository is a node that represents a specific application in AppEnhancer. This node allows Grooper to interoperate with the AppEnhancer application.

	== Importing and Exporting with AppXtender ==		== Importing and Exporting with AppXtender ==

Dgreenwood at 17:10, 16 May 2025

2025-05-16T17:10:13Z

← Older revision		Revision as of 12:10, 16 May 2025
Line 5:		Line 5:
	<blockquote>{{#lst:Glossary\|AppXtender}}</blockquote>		<blockquote>{{#lst:Glossary\|AppXtender}}</blockquote>

	~~ApplicationXtender~~ is a content management system ~~utilizing Microsoft~~.~~NET capabilities~~ to store documents and associated ~~metadata~~ online. It stores documents in ~~file cabinets it calls~~ "applications"~~. Creating an AppXtender connection will allow you to access an existing AX file cabinet. Once connected, you can import, export, search, and browse documents from Grooper.~~		== About ==
	~~<br clear=all>~~		AppEnhancer is a "[https://en.wikipedia.org/wiki/OpenText#OpenText_AppEnhancer_(formerly_ApplicationXtender) content management system that manages, organizes, and stores information from an application or as an extension to an existing application.]" It is an effective tool used to store documents and field data associated with those documents. AppEnhancer has both onprem and online capabilities. AppEnhancer stores documents in storage locations they call "applications".
	~~== Version Differences ==~~
	Prior to 2.72, you would have used the old CMIS Import and CMIS Export Providers. The old CMIS Import still exists in Grooper as a deprecated component. CMIS Export has been split into Mapped and Unmapped Export providers (Mapped Export being similar to how CMIS Export formerly functioned). For increased functionality in 2.72, create an AppExtender Connection Type and utilize the new CMIS Import and CMIS Export capabilities.

	~~In order~~ to ~~connect~~ to ApplicationXtender ~~in versions before 2~~.~~72, you had to create~~ a ~~Grooper Service to facilitate the~~ connection. ~~You no longer have to do that utilizing~~ the ~~AppXtender CMIS binding. Creating a new~~ connection to ~~AppXtender is now~~ as ~~simple~~ as ~~creating a new~~ CMIS Connection ~~and editing~~ a ~~few properties~~.		The AppXtender binding is used to provide Grooper connectivity to AppEnhancer (formerly ApplicationXtender) applications. "AppXtender" can be selected as a connection option when configuring a CMIS Connection. After configuring the connection, AppEnhancer applications are exposed to Grooper as a CMIS Repository. CMIS Repository nodes are created as children of the CMIS Connection by importing a reference to their source location.

			The AppXtender CMIS Repository allows Grooper to "see" documents in the AppEnhancer application. Once a CMIS Repository is created, you can import, export, search, and browse documents from Grooper.
			* The AppXtender binding can be used for import operations via [[CMIS Import]] using "Import Descendants" or "Import Query Results".
			* It can be used for export operations via [[CMIS Export]].
			** AppXtender can be used for simpler "unmapped" exports, if you just want to export Grooper documents as files to an AppEnhancer application with no additional metadata fields.
			** AppXtender can also be used for "mapped" exports.
			*** AppEnhancer applications allow the platform to store additional document data as fields.
			*** Extracted '''Data Field''' values in Grooper can be exported to fields in the application along with the document's file.
			*** In the [[CMIS Export]] setup, a Data Field in Grooper is mapped to a corresponding field in the AppEnhancer application. When the document is exported the value is copied from Grooper and entered into the mapped field in AppEnhancer.<br clear=all>
	=== Name Changes ===		=== Name Changes ===
			'''ApplicationXtender''' is now '''''AppEnhancer'''''.
	ApplicationXtender is now AppEnhancer.		<li class="attn-bullet"> Be aware the CMIS Binding's name is still "''AppXtender''" in Grooper.
	<li class="attn-bullet"> Be aware the CMIS Binding's name is still "AppXtender" in Grooper.
	<li class="attn-bullet"> AppEnhancer may still be referred to as ApplicationXtender, AppXtender or AX by Grooper users and documentation.		<li class="attn-bullet"> AppEnhancer may still be referred to as ApplicationXtender, AppXtender or AX by Grooper users and documentation.

Dgreenwood: /* Name Changes */

2025-05-16T16:56:13Z

Name Changes

← Older revision		Revision as of 11:56, 16 May 2025
Line 13:		Line 13:

	=== Name Changes ===		=== Name Changes ===
	~~As of December 15, 2021~~ ApplicationXtender ~~(also known~~ as AppXtender, or AX ~~for short) has changed its name to AppEnhancer. Users~~ and ~~Grooper use all terms interchangeably~~.
			ApplicationXtender is now AppEnhancer.
			<li class="attn-bullet"> Be aware the CMIS Binding's name is still "AppXtender" in Grooper.
			<li class="attn-bullet"> AppEnhancer may still be referred to as ApplicationXtender, AppXtender or AX by Grooper users and documentation.

	== How to create an AppEnhancer connection ==		== How to create an AppEnhancer connection ==