Default batch process list
Kuroco provides the following default batch processes. Executing a batch process will incur pay-as-you-go computing charges. Therefore, please enable or disable your processes as needed on the batch process screen. The operational details of the available processes are listed below by module.
E-commerce
ec_process_download
Executed: Every 15 minutes when there are orders for downloadable products.
Description: Handle downloadable product sales and execute a series of processes to download the target products.
ec_auto_sale_regular
Executed: Every 15 minutes when there are orders for subscription products.
Description: Handle sales of subscription products.
ec_order_expire_cancel
Executed: Daily at 3 a.m.
Description: Cancel an order that is past due for payment.
ec_regular_delivery_download
Executed: Daily at 2 a.m. when there are orders for downloadable subscription products.
Description: Handle sales of downloadable subscription products.
API
cache_update
Executed: When [Clear cache] is clicked on the /management/rcms_api/api_list/?api_id=**
screen.
Description: Clear the API settings cache.
api_exec
Executed: When the API is requested asynchronously (only for asynchronous APIs).
Description: Execute the specified batch process.
Content
topics_cleanup_update_history
Executed: When updated with [Do not leave update history] enabled on the /management/topics/topics_group_edit/?topics_group_id=**
screen.
Description: Delete the content update history.
topics_bulk_postprocess
Executed: After a batch content upload.
Description: Perform the necessary processes after the batch content upload (e.g., recalculation of the number of related tags).
sync_counter
Executed: Hourly
Description: Synchronize the number of accesses obtained from GA to each content group.
topics_group_settings_postupdate
Executed: After updating the content structure editor.
Description: Execute the necessary processes after editing and updating the content structure (e.g., database index rebuilding).
topics_upload
Executed: When [Send by batch processing] is clicked on the /management/topics/topics_upload/?topics_group_id=**
screen.
Description: Upload content by selecting [Send by batch processing].
topics_download
Executed: When [Send by batch processing] or [File download by batch processing] is clicked on the /management/topics/topics_list/?topics_group_id=**
screen.
Description: Download contents or files via batch processing.
External system integration
vaddy
Executed: When [Update] is clicked on the /management/external/vaddy/
screen.
Description: External API; perform vulnerability assessment using VAddy.
Member
member_provisional_upload
Executed: When [Send by batch processing] is clicked on the /management/member/member_provisional_upload/
screen.
Description: Batch upload temporary member information.
member_lump
Executed: When [Send by batch processing] is clicked on the /management/member/member_upload/
screen.
Description: Upload members by selecting [Send by batch processing].
loginid_remainder_to_user
Executed: 30 days before login permission expires for the target member (see corresponding /management/member/member_edit/?member_id=**
screen).
Description: Send an e-mail notification to the user one month prior to their login ID expiration date.
Notification
magazine_sendmail_bat
Executed: Scheduled delivery time (see corresponding /management/magazine/magazine_sendmail_edit/?magazine_id=**
screen).
Description: Specify the delivery date and time in the notification editor to set up the batch process.
Form
inquiry_bn_download
Executed: When [Download file] or [File download by batch processing] is clicked on the /management/inquiry/inquiry_bn_list/inquiry_id=**
screen.
Description: Download data or attached files for the form responses.
Batch processes
openflgSetting
Executed: Scheduled publication time of the target content group.
Description: Set the content group as public or private based on the publication time. Specifying a publication date and time for the content group will set up the batch process at the same time.
Workflow
scheduled_publish
Executed: Scheduled publication time of the target approval workflow.
Description: Approve time-limited data that is awaiting approval.
approval_alert
Executed: Upon reaching the specified "days until alert" after creating the workflow (see the corresponding /management/approvalflow/approvalflow_edit/?approvalflow_id=**
screen).
Description: An approval request notification will be sent to the designated approver if there is data awaiting approval.