About Delivered Message Parts

The following message parts are delivered with the standard installation of Aptify.

About the Address Update Message Part

This sample part illustrates how an administrator can create a part that interacts with an Aptify e-Business website to allow recipients of a message to update their address directly from the received email. Since this part uses HTML code, it only has an HTML implementation (there is no corresponding Plain Text version). This part rendered a person's address information in a series of text boxes that can be modified and then submitted back to the e-Business server when a recipient clicks the Submit button.

The rendered preview for this part is shown below. Keep in mind that this part is not functional by default; it requires a Web developer to create a page that can process the update information back into Aptify and requires an administrator to update the part to specify the correct website URL where updates should be directed.

Address Update Part


About the Data Table Message Part

This is a script-based generic message part that creates a data table using input values provided by a derived message part (such as Other People at Same Company Table). See Creating a Generic Base Part for more information on this type of message part. This data table supports the following input properties:

  • SQL: A source SQL statement that populates the table. This is required to generate and display a data table.
  • Title: Specifies a title for the rendered table.
  • CellSpacing: The amount of spacing in pixels placed between the HTML cells (for an HTML message).
  • CellPadding: The amount of padding in pixels added to each HTML cell (for an HTML message).
  • Border: Determines if the table when rendered for an HTML message should use -borders (0 = no borders; 1 = borders).


About the Extended Data Table Message Part

This is a script-based generic message part that creates a data table using input values provided by a derived message part (such as Order Lines). It provides more formatting options than the standard Data Table part. See Creating a Generic Base Part for more information on this type of message part. This data table supports the following input properties:

  • SQL: A source SQL statement that populates the table. This is required to generate and display a data table.
  • Title: Specifies a title for the rendered table.
  • TitleFont: This property accepts a complete FONT tag to set the font for the title. For example: <font face="Tahoma" size="2" color="White"><b>.
  • CellSpacing: The amount of spacing in pixels placed between the HTML cells (for an HTML message).
  • CellPadding: The amount of padding in pixels added to each HTML cell (for an HTML message).
  • Border: Determines if the table when rendered for an HTML message should use -borders (0 = no borders; 1 = borders).
  • HeaderCellAttributes: Specifies attributes to add to the TD tag for the table header cells (such as bgcolor="white" valign="top").
  • RowCellAttributes: Specifies attributes to add to the TD tag for every other table body row (first, third, fifth, etc.).
  • AlternateRowAttributes: Specifies attributes to add to the TD tag for the alternating rows in the table's body (second, fourth, sixth, etc.).
  • HeaderFont: This property accepts a complete FONT tag to set the font for the header cells.
  • RowFont: This property accepts a complete FONT tag to set the font for the first, third, fifth, etc. rows in the table.
  • AlternateRowFont: This property accepts a complete FONT tag to set the font for the alternating rows in the table.
  • ShowLine: Set this input property to 1 to display a line above the data table (to separate it from other areas of the message). Set this to 0 to omit the line.
  • AddSummaryRow: Set to 1 to add a summary row to the bottom of the table. For numeric columns, this row displays the total for that column by adding together the values in the individual cells. Set this to 0 to omit a summary row.


About the Meeting City Message Part

This script-based message part provides the city in which the meeting is taken place, based on the Meeting location's address information.


About the Meeting Details Message Part

This part uses a SQL statement to specify that the Meeting Title Base Part should display a table with information about the meeting details from a particular order. See Creating a Derived Part for more information on this type of message part.

This part uses the following SQL statement to populate the Data Table:

SELECT m.SessionWParent AS 'Meeting',m.StartDate AS 'Start Date and Time',omd.AttendeeID_Name As 'Registrant',omd.AttendeeStatus_Name As 'Current Status' FROM dbo.vwOrderMeetDetail omd INNER JOIN dbo.vwMeetings m On omd.ProductID=m.ProductID WHERE omd.OrderID=<%ID%> ORDER BY omd.AttendeeID_Name,m.StartDate

 

The remaining input properties specify formatting options for the table. See the Message Parts record's Input Map tab for details.


About the Meeting Location Message Part

This script-based message part provides the location of the meeting, based on the Place field in the linked Meetings record.


About the Meeting StartDate Message Part

This script-based message part provides the start date of the linked meeting.


About the Meeting State Message Part

This script-based message part provides the state in which the meeting is taken place, based on the Meeting location's address information.


About the Meeting Title Message Part

This is a script-based message part that displays the Meeting Title (from the Meetings record linked to a campaign).


About the Meeting URL Message Part

This script-based message part provides the website location of the meeting. This information is based on the Web Page field from the linked Meeting's Products record.


About the One Line Address Block Message Part

This part adds the following fields from a record to a message:

  • AddressLine1
  • City
  • State
  • ZipCode
  • Country


About the Order History Part Message Part

This part uses a SQL statement to specify that the Data Table Base Part should display a table of the orders where the message recipient is the Ship To person. See Creating a Derived Part for more information on this type of message part.

This part provides these input values for the Data Table:

  • SQL: SELECT ID, OrderDate 'Order Date', Line1_ProductName 'Product Name', CALC_GrandTotal 'Grand Total' FROM APTIFY.dbo.vwOrders WHERE ShipToID=<%ID%>
  • Title: This is your order history

Note that the other optional input properties are not specified, and they use default HTML settings.


About the Order Lines Message Part

This part uses a SQL statement to specify that the Meeting Title Base Part should display a table with information the order lines from a particular order. See Creating a Derived Part for more information on this type of message part.


This part uses the following SQL statement to populate the Data Table:

  • SQL: SELECT Description, Quantity, Price, Discount, Extended FROM APTIFY..vwOrderDetails WHERE OrderID=<%ID%> ORDER BY Sequence

The remaining input properties specify formatting options for the table. See the Message Parts record's Input Map tab for details.


About the Other People at Same Company Table Message Part

This part uses a SQL statement to specify that the Data Table Base Part should display a table of all other Persons who are at the same company as the message recipient. See Creating a Derived Part for more information on this type of message part.


This part provides these input values for the Data Table:

  • SQL: SELECT FirstName,LastName,Title,Email1,CompanyID FROM APTIFY.dbo.vwPersons WHERE CompanyID=<%CompanyID%> AND ID<><%ID%> ORDER BY LastName, FirstName
  • Title: People at Your Company in OUR DB

Note that the other optional input properties are not specified, and they use default HTML settings.

 

About the Two-Line Address Block Message Part

This part adds the same information as the One Line Address Block part, except this part adds the AddressLine2 field.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.