2023:Exchange (CMIS Binding) - Revision history

Dgreenwood: Dgreenwood moved page 2023:Exchange (CMIS Connection Type) to 2023:Exchange (CMIS Binding)

2025-05-13T15:22:13Z

Dgreenwood moved page 2023:Exchange (CMIS Connection Type) to 2023:Exchange (CMIS Binding)

← Older revision	Revision as of 10:22, 13 May 2025
(No difference)

Randallkinard at 19:26, 21 November 2024

2024-11-21T19:26:59Z

← Older revision		Revision as of 14:26, 21 November 2024
Line 191:		Line 191:
	** Correct syntax: <code>Sender LIKE '%user@example.com%'</code>		** Correct syntax: <code>Sender LIKE '%user@example.com%'</code>
	<section end="exchange_query_limitations" />		<section end="exchange_query_limitations" />

	~~== Glossary ==~~
	~~<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}~~

	~~<u><big>'''CMIS Connection Type'''</big></u>: {{#lst:Glossary\|CMIS Connection Type}}~~

	~~<u><big>'''CMIS Connection'''</big></u>: {{#lst:Glossary\|CMIS Connection}}~~

	~~<u><big>'''CMIS Export'''</big></u>: {{#lst:Glossary\|CMIS Export}}~~

	~~<u><big>'''CMIS Import'''</big></u>: {{#lst:Glossary\|CMIS Import}}~~

	~~<u><big>'''CMIS Repository'''</big></u>: {{#lst:Glossary\|CMIS Repository}}~~

	~~<u><big>'''CMIS'''</big></u>: {{#lst:Glossary\|CMIS}}~~

	~~<u><big>'''Correct'''</big></u>: {{#lst:Glossary\|Correct}}~~

	~~<u><big>'''Exchange'''</big></u>: {{#lst:Glossary\|Exchange}}~~

	~~<u><big>'''Execute'''</big></u>: {{#lst:Glossary\|Execute}}~~

	~~<u><big>'''Export'''</big></u>: {{#lst:Glossary\|Export}}~~

	~~<u><big>'''Import Query Results'''</big></u>: {{#lst:Glossary\|Import Query Results}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Repository'''</big></u>: {{#lst:Glossary\|Repository}}~~

Randallkinard at 16:10, 26 August 2024

2024-08-26T16:10:41Z

@@ Line 6: / Line 6: @@
 The '''''Exchange''''' '''''Connection Type''''' allows you to access Outlook files and folders.  You can access mail messages, calendar appointments, contact cards, and tasks all using this binding.  Once connected, you can import full mail message threads and attached files into Grooper.
 == Version Differences ==
@@ Line 220: / Line 191: @@
 ** Correct syntax:  <code>Sender LIKE '%user@example.com%'</code>
 <section end="exchange_query_limitations" />

Randallkinard at 18:23, 8 May 2024

2024-05-08T18:23:26Z

@@ Line 6: / Line 6: @@
 The '''''Exchange''''' '''''Connection Type''''' allows you to access Outlook files and folders.  You can access mail messages, calendar appointments, contact cards, and tasks all using this binding.  Once connected, you can import full mail message threads and attached files into Grooper.
 == Version Differences ==
 Prior to version 2.72, connections to Exchange servers were made using the Mail Import and Mail Export providers. The '''''Exchange''''' binding replaces the old '''''Mail Import''''' provider and provides increased functionality. '''''Mail Import''''' is still available as a "legacy" provider. While these providers still exists in Grooper as legacy import and export providers, they are deprecated components and no longer recommended for use.

Randallkinard at 21:00, 19 April 2024

2024-04-19T21:00:55Z

← Older revision		Revision as of 16:00, 19 April 2024
Line 1:		Line 1:
	{{AutoVersion}}		{{AutoVersion}}

	[[image:exchange.png\|frame]]		[[image:exchange.png\|frame]]
	~~<section begin="glossary" />~~
	<blockquote>		<blockquote>{{#lst:Glossary\|Exchange}}</blockquote>
	~~The '''''~~Exchange~~''''' '''''Connection Type''''' is a '''''CMIS Binding''''' that connects Grooper to email messages and folders through a Microsoft Exchange Server.~~
	</blockquote>
	~~<section end="glossary" />~~
	The '''''Exchange''''' '''''Connection Type''''' allows you to access Outlook files and folders. You can access mail messages, calendar appointments, contact cards, and tasks all using this binding. Once connected, you can import full mail message threads and attached files into Grooper.		The '''''Exchange''''' '''''Connection Type''''' allows you to access Outlook files and folders. You can access mail messages, calendar appointments, contact cards, and tasks all using this binding. Once connected, you can import full mail message threads and attached files into Grooper.

Line 15:		Line 14:

	== How To: Create a New Exchange Connection ==		== How To: Create a New Exchange Connection ==

	<tabs>		<tabs>
	<tab name="Step 1">		<tab name="Step 1">

Randallkinard: Randallkinard moved page 2023:Exchange (CMIS Binding) to 2023:Exchange (CMIS Connection Type) without leaving a redirect: new naming convention

2024-04-17T14:52:02Z

Randallkinard moved page 2023:Exchange (CMIS Binding) to 2023:Exchange (CMIS Connection Type) without leaving a redirect: new naming convention

← Older revision	Revision as of 09:52, 17 April 2024
(No difference)

Dgreenwood: /* Exchange CMISQL Query Limitations */

2024-04-10T21:20:41Z

Exchange CMISQL Query Limitations

← Older revision		Revision as of 16:20, 10 April 2024
Line 185:		Line 185:
	== Known Issues & Limitations ==		== Known Issues & Limitations ==
	=== Exchange CMISQL Query Limitations ===		=== Exchange CMISQL Query Limitations ===
			<section begin="exchange_query_limitations" />
			When configuring a <code>WHERE</code> clause (using a '''''Comparison Predicate'''''), the "Subject", "Sender", "To Recipients", "Cc Recipients", and "Bcc Recipients" cannot use the <code>=</code> operator.
			* Use the <code>LIKE</code> operator instead.
			** Incorrect syntax: <code>Sender = '%user@example.com%'</code>
			** Correct syntax: <code>Sender LIKE '%user@example.com%'</code>
			* '''''BE AWARE:''''' EWS only supports substring matching for these properties. You must use the <code>%</code> wildcard on either side of the search term when using the <code>LIKE</code> operator.
			** Incorrect syntax: <code>Sender LIKE 'user@example.com'</code>
			** Correct syntax: <code>Sender LIKE '%user@example.com%'</code>
			<section end="exchange_query_limitations" />

Dgreenwood: /* Exchange Query Examples */

2024-04-10T20:12:27Z

Exchange Query Examples

← Older revision		Revision as of 15:12, 10 April 2024
Line 159:		Line 159:
	\|}		\|}

	== Exchange Query Examples ==		== Exchange CMISQL Query Examples ==

	You can search across all item types, including searching for e-mail messages. A use for this could be using Import Query Results to narrow down what you want to import across ~~several~~ mailboxes.		You can search across all item types, including searching for e-mail messages. A use for this could be using '''''Import Query Results''''' to narrow down what you want to import across one or more mailboxes based on sender and/or words in the subject line.

	=== Query 1 ===		=== Query 1 ===
Line 172:		Line 172:
	This query would search the Message content type for certain property values. Namely, that the messages have attachment, contain the words "Sales Order" and "grooper" in the title and were received after Jan 01, 2018.		This query would search the Message content type for certain property values. Namely, that the messages have attachment, contain the words "Sales Order" and "grooper" in the title and were received after Jan 01, 2018.

	Note you cannot search for identity in a subject line. You cannot use the <code>=</code> operator to search for something in a subject. Instead, use the <code>LIKE</code> ~~predicate~~. Search using grammar like this: <code>Subject LIKE '%put what you're searching for here%'</code>		Note you cannot search for "identity" in a subject line.
			* You cannot use the <code>=</code> operator to search for something in a subject.
			* Instead, use the <code>LIKE</code> operator. Search using grammar like this: <code>Subject LIKE '%put what you're searching for here%'</code>

	=== Query 2 ===		=== Query 2 ===
Line 179:		Line 181:
	WHERE CONTAINS ('grooper AND 2023 AND beta')</code>		WHERE CONTAINS ('grooper AND 2023 AND beta')</code>

	You can also search across all ~~document~~ types. This query would return any Messages, Contacts, Appointments or Tasks that have the words "grooper" "2023" and "beta" in their text (including subject lines). You also have access to <code>OR</code> and <code>NOT</code> operators.		You can also search across all content types. This query would return any Messages, Contacts, Appointments or Tasks that have the words "grooper" "2023" and "beta" in their text (including subject lines). You also have access to <code>OR</code> and <code>NOT</code> operators.

			== Known Issues & Limitations ==
			=== Exchange CMISQL Query Limitations ===

Dgreenwood: /* Exchange Binding Content Types */

2024-04-10T20:02:15Z

Exchange Binding Content Types

← Older revision		Revision as of 15:02, 10 April 2024
Line 93:		Line 93:
	== Exchange Binding Content Types ==		== Exchange Binding Content Types ==

	The Exchange Binding has ~~four~~ content types, Messages, Appointments, Contacts, and Tasks. Each one has its own set of properties you can query using CMISQL queries (Either using a CMIS Repository's "Search Tab" or using '''''Import Query Results''''' to import files from an inbox. ~~All four~~ content ~~types are full text searchable. There~~ is ~~also~~ a base type ~~"Item"~~ which all four content types inherit. It ~~is also full-text searchable, defining~~ a common set of properties to ~~all~~ four ~~document~~ types.		The Exchange Binding has five "content types": Item, Messages, Appointments, Contacts and Tasks. Each one has its own set of properties you can query using CMISQL queries (Either using a CMIS Repository's "Search Tab" or using '''''Import Query Results''''' to import files from an inbox). The "Item" content type is a base type from which all four content types inherit. It defines a common set of properties to the other four content types. All five content types are full text searchable using the <code>CONTAINS()</code> predicate.

	{\|cellpadding="10" cellspacing="10"		{\|cellpadding="10" cellspacing="10"
	\|'''Content Type'''\|\|'''Description'''\|\|'''Properties'''		\|'''Content Type'''\|\|'''Description'''\|\|'''Properties'''
			\|-valign="top"
			\|Item
			\|The base type item, which all content types inherit.

			'''Users should ''only'' query using this content type if they want to return files of all types (Messages, Appointments, Contacts and Tasks).'''
			\|
			* Subject
			* Size
			* Has Attachments
	\|-valign="top"		\|-valign="top"
	\|Message		\|Message
	\|Represents an email message.		\|Represents an email message.
	'''This is the most commonly used Exchange ~~Content Type~~.'''		'''This is the most commonly used Exchange content type.'''
	'''Most typically users want to query/import email messages.'''		'''Most typically users want to query/import email messages.'''

Line 114:		Line 123:
	* Date Time Sent		* Date Time Sent
	* Is Read		* Is Read
	* Size
	* Has Attachments
	~~\|-valign="top"~~
	~~\|Item~~
	~~\|The base type item, which all document types inherit~~
	\|
	* Subject
	* Size		* Size
	* Has Attachments		* Has Attachments

Dgreenwood: /* Exchange Binding Content Types */

2024-04-10T19:56:15Z

Exchange Binding Content Types

@@ Line 93: / Line 93: @@
 == Exchange Binding Content Types ==
-The Exchange Binding has four content types, Messages, Appointments, Contacts, and Tasks.  Each one has its own set of properties you can query using the "Search Repository" tab when selecting an imported repository.  All four content types are full text searchable.  There is also a base type "Item" which all four content types inherit.  It is also full-text searchable, defining a common set of properties to all four document types.
+The Exchange Binding has four content types, Messages, Appointments, Contacts, and Tasks.  Each one has its own set of properties you can query using CMISQL queries (Either using a CMIS Repository's "Search Tab" or using '''''Import Query Results''''' to import files from an inbox.  All four content types are full text searchable.  There is also a base type "Item" which all four content types inherit.  It is also full-text searchable, defining a common set of properties to all four document types.
 {|cellpadding="10" cellspacing="10"
 |'''Content Type'''||'''Description'''||'''Properties'''
 |-valign="top"
 |Appointment
@@ Line 117: / Line 143: @@
 * Display Name
 * Subject
 * Size
 * Has Attachments
@@ Line 142: / Line 151: @@
 * MIME Type: text/plain
 * File Extension: .txt
+|
 * Subject

← Older revision		Revision as of 14:26, 21 November 2024
Line 191:		Line 191:
	** Correct syntax: <code>Sender LIKE '%user@example.com%'</code>		** Correct syntax: <code>Sender LIKE '%user@example.com%'</code>
	<section end="exchange_query_limitations" />		<section end="exchange_query_limitations" />

	~~== Glossary ==~~
	~~<u><big>'''AND'''</big></u>: {{#lst:Glossary\|AND}}~~

	~~<u><big>'''CMIS Connection Type'''</big></u>: {{#lst:Glossary\|CMIS Connection Type}}~~

	~~<u><big>'''CMIS Connection'''</big></u>: {{#lst:Glossary\|CMIS Connection}}~~

	~~<u><big>'''CMIS Export'''</big></u>: {{#lst:Glossary\|CMIS Export}}~~

	~~<u><big>'''CMIS Import'''</big></u>: {{#lst:Glossary\|CMIS Import}}~~

	~~<u><big>'''CMIS Repository'''</big></u>: {{#lst:Glossary\|CMIS Repository}}~~

	~~<u><big>'''CMIS'''</big></u>: {{#lst:Glossary\|CMIS}}~~

	~~<u><big>'''Correct'''</big></u>: {{#lst:Glossary\|Correct}}~~

	~~<u><big>'''Exchange'''</big></u>: {{#lst:Glossary\|Exchange}}~~

	~~<u><big>'''Execute'''</big></u>: {{#lst:Glossary\|Execute}}~~

	~~<u><big>'''Export'''</big></u>: {{#lst:Glossary\|Export}}~~

	~~<u><big>'''Import Query Results'''</big></u>: {{#lst:Glossary\|Import Query Results}}~~

	~~<u><big>'''Project'''</big></u>: {{#lst:Glossary\|Project}}~~

	~~<u><big>'''Repository'''</big></u>: {{#lst:Glossary\|Repository}}~~