Custom App Funtion: Custom App
## Overview
"「Custom App」" allows you to register templates of business applications made up of multiple folders and tables commonly used in Pleasanter, making it easy to reuse. By registering packages that include tables with linked structures, summaries, lookups, and other settings, you can quickly create groups of sites with the same structure for future projects or business tasks, improving work efficiency.
Custom App is a function that registers a template from a Json file created by the site package export function, based on the site structure and settings you have created.
## Key Features
1. You can register entire site groups, including linked tables with parent-child relationships and folders, as templates.
1. It is possible to register with multiple tables configured across links, summaries, lookups, etc.
1. By registering commonly used table structures and business processes as custom apps, you can reuse them for similar projects and tasks, improving efficiency.
## Limitations
1. Attachments and images cannot be registered.
1. If the topmost folder of the site that the custom app is based on has inherited access rights, the access rights will not be correctly set during the creation of the custom app, and the site will be inaccessible. When creating the site for the custom app, please perform the creation from a folder that does not inherit access rights.
1. If scripts are embedded and specify site IDs or record IDs, the IDs will change, which may cause them to not work correctly. The IDs specified in the script need to be manually updated.
1. When registering a site package exported from a different Pleasanter as a custom app, the dept, group, and user information stored in records will not be converted to the destination's ID.
## Prerequisites
1. "Tenant Management Permissions" are required.
## Related Information
<div id="ManualList">
<article class="s-blog_list_unit"><h2>
<h2>The specified information was not found.</h2>
<p><a href="/ja/manual">Return to top</a></p>
</article>
</div><input id="SearchTextHidden" type="hidden" value="" />