Entando Plugin: Content Scheduler

CMS Content Scheduler

License	GNU LESSER GENERAL PUBLIC LICENSE, Version 2.1, February 1999
GroupId	org.entando.entando.plugins
ArtifactId	entando-plugin-jpcontentscheduler
Last Version	6.2.6
Release Date	Oct 20, 2020
Type	war
Description	Entando Plugin: Content Scheduler CMS Content Scheduler
Project URL	http://www.entando.com/
Project Organization	Entando Inc.

Download entando-plugin-jpcontentscheduler

Filename	Size
entando-plugin-jpcontentscheduler-6.2.6.pom
entando-plugin-jpcontentscheduler-6.2.6.war	105 MB
entando-plugin-jpcontentscheduler-6.2.6-tests.jar	12 KB
entando-plugin-jpcontentscheduler-6.2.6-sources.jar	65 KB
entando-plugin-jpcontentscheduler-6.2.6-javadoc.jar	178 KB
entando-plugin-jpcontentscheduler-6.2.6-classes.jar	73 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.entando.entando.plugins/entando-plugin-jpcontentscheduler/ -->
<dependency>
    <groupId>org.entando.entando.plugins</groupId>
    <artifactId>entando-plugin-jpcontentscheduler</artifactId>
    <version>6.2.6</version>
    <type>war</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.entando.entando.plugins/entando-plugin-jpcontentscheduler/
implementation 'org.entando.entando.plugins:entando-plugin-jpcontentscheduler:6.2.6'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.entando.entando.plugins/entando-plugin-jpcontentscheduler/
implementation ("org.entando.entando.plugins:entando-plugin-jpcontentscheduler:6.2.6")

Apache Buildr

'org.entando.entando.plugins:entando-plugin-jpcontentscheduler:war:6.2.6'

Apache Ivy

<dependency org="org.entando.entando.plugins" name="entando-plugin-jpcontentscheduler" rev="6.2.6">
  <artifact name="entando-plugin-jpcontentscheduler" type="war" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.entando.entando.plugins', module='entando-plugin-jpcontentscheduler', version='6.2.6')
)

Scala SBT

libraryDependencies += "org.entando.entando.plugins" % "entando-plugin-jpcontentscheduler" % "6.2.6"

Leiningen

[org.entando.entando.plugins/entando-plugin-jpcontentscheduler "6.2.6"]

Dependencies

compile (4)

Group / Artifact	Type	Version
org.entando.entando.plugins : entando-plugin-jacms	jar	6.2.17
org.entando.entando : entando-portal-ui	jar	6.2.6
org.entando.entando.plugins : entando-plugin-jpmail	jar	6.2.5
org.springframework : spring-tx	jar	5.1.8.RELEASE

provided (2)

Group / Artifact	Type	Version
javax.servlet : javax.servlet-api	jar	3.1.0
javax.servlet.jsp : jsp-api	jar	2.2

test (13)

Group / Artifact	Type	Version
org.entando.entando.plugins : entando-plugin-jacms	test-jar	6.2.17
org.entando.entando.plugins : entando-plugin-jpmail	test-jar	6.2.5
org.entando.entando : entando-engine	test-jar	6.2.23
org.entando.entando : entando-admin-console	test-jar	6.2.36
org.entando.entando : entando-portal-ui	test-jar	6.2.6
org.springframework : spring-test	jar	5.1.8.RELEASE
org.mockito : mockito-core	jar	2.28.2
org.assertj : assertj-core	jar	3.11.1
org.hamcrest : hamcrest-all	jar	1.3
com.jayway.jsonpath : json-path-assert	jar	2.2.0
org.apache.derby : derbyclient	jar	10.9.1.0
org.apache.derby : derby	jar	10.9.1.0
junit : junit	jar	4.12

Project Modules

There are no modules declared in this project.

entando-plugin-jpcontentscheduler

Content scheduler

Code: jpcontentscheduler

Description

This plugin is used to manage contents temporal windows based on the content's dates.

It is possible to set up rules that:

• will move an expired content to a public archive
• will unpublish the expired content
• will automatically publish the content
• will send email notifications to a list of users

Installation

Open the pom.xml of your project: locate the tag toward the end of the file, after the tag; if the dependencies tag does not exist just create a new one just after the closure of the build tag.

Add the following snippet inside the dependencies:

<dependency>
    <groupId>org.entando.entando.plugins</groupId>
    <artifactId>entando-plugin-jpcontentscheduler</artifactId>
    <version>${entando.version}</version>
    <type>war</type>
</dependency>

General Settings:

• Active boolean used to enable or disable the plugin

• SiteCode configuration parameter related to the clustering plugin

• Global category mandatory category code that each content will be assigned to when suspended or moved to a generic archive not belonging to a specific category

• Content replacement content identifier that will replace the archived/unpublished content

• Content model replacement model identifier that will replace the archived/unpublished content

Email Settings:

These settings are used to manage how email notifications are being sent

Users Settings:

Used to define bindings between users and content types. It is possible to specify in a very granular way which user should receive emails for each type of content.

Content Types Settings:

• start date attribute this mandatory parameter defines the mapping of the field used for automatic publishing.

• end date attribute this mandatory parameter defines the mapping of the field used to determine whether or not the content has expired.

• Content replace id this optional parameter overrides the General Settings Content replacement setting.

• Content replace model id this optional parameter overrides the General Settings Content model replacement setting.

• Suspend mandatory boolean to define the behaviour of an expired content: true unpublishes the content while false archives it.

Developing against local versions of upstream projects (e.g. admin-console, entando-engine).

Full instructions on how to develop against local versions of upstream projects are available in the entando-parent-bom project.

Entando Inc

Open source micro frontend platform for Kubernetes.

Versions

Version
6.2.6 Oct 20, 2020
6.1.1 Apr 24, 2020
6.1.0 Apr 14, 2020
5.3.2 Apr 26, 2021
5.3.1 Sep 8, 2020
5.2.0 Jul 19, 2019
5.1.0 Apr 4, 2019
5.0.3 Mar 8, 2019
5.0.2 Nov 26, 2018
5.0.1 Nov 16, 2018
5.0.0 May 29, 2018
4.3.2 Feb 23, 2018
4.3.1 Jul 14, 2017