User Logs can now be "Repeated" on a specified cycle upon completion

The "Other" page of a User Log now includes a new section, "Log Repeat details". This allows a Log to automatically generate another User Log with an Action Date generated from the combination of the repeat Basis & Cycle. The following properties of the existing Log are copied across to the new one:

• Subject
• Notes
• Owner
• Delegated to (Role or User)
• Log Severity
• User Pk
• Source
• Repeat information ('use' flag, Basis & Cycle)

In Scripting, the following Properties on finUserLog can be used to configure a repeating Log:

• RepeatBasis
• RepeatCycle (accepts a Cycle Mnemonic)
• RepeatUse
• RepeatUseResolved (checks the RepeatUse Property as well as the CanRepeat() function)

Currently, only the following sources support repeating Logs:

• ExternalA to ExternalJ
• ExternalReadOnlyA to ExternalReadOnlyJ
• Unknown
• UserInterface
• WebInterface
• WebServices
• CloudConnect
• WorkflowIncomingCommunicationUserInterface
• WorkflowOutgoingCommunicationUserInterface
• Portal

Also, if any User Log has a Document Id attached (regardless of Source) the Log cannot be repeated.

Note: Initially, only User Logs support repeating; in the future this may be expanded to the other Log types. Additionally, HTML Widgets and finPOWER Connect Cloud do not support repeating Logs. This support will be added at such time support for other Log types is added.