<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3locallangExt>
	<data type="array">
		<languageKey index="ch" type="array">
			<label index=".description">“动作”是一个特殊的作业的配置，该作业由用户组通过任务中心分配任务。</label>
			<label index=".details">当前一个动作可能被配置为不通过管理员用户并只选择一些选项设置来创建一个附加的后台用户组。另一个动作是让动作开始一个SQL查询并作为CVS文件返回结果。
动作可被分配给后台用户组，并可在任务中心简单地点击以激活。</label>
			<label index="title.description">输入动作的标题。该标题将显示在任务中心的可用的动作列表中。</label>
			<label index="description.description">描述动作做什么或允许做什么。</label>
			<label index="hidden.description">如果您希望禁用可用的动作或非管理员用户，请选择此选项。</label>
			<label index="hidden.details">该选项是在改变动作期间禁用一个动作的一个很好的方法，因为它依然允许您作为“管理”用户来激活它以进行测试。</label>
			<label index="type.description">选择动作类型。</label>
			<label index="type.details">&lt;strong&gt;&quot;创建后台用户&quot;&lt;/strong&gt;允许通过有限的设置选项来创建后台用户。此动作类型 is meant for semi-administrators among your users which is in charge of daily user administration - still without being full fledged 'Admin'-users with 'a License to Kill everything'.
当您选择此选项，您进入了一个“模板”用户，输入自动创建的新用户的名称的前缀以及是否创建用户的主目录。最终您可选择他们能选择属于的的用户组的限制数。
&lt;strong&gt;&quot;SQL-查询&quot;&lt;/strong&gt; 允许构造一个固定的SQL SELECT-查询到数据库中并作为CSV列表返回。当您创建了此类型的一个动作后，您需要前往工具&gt;数据库检查模块并进入高级搜索特性。在这里您可定义您的SQL查询。当您设计它为您所需要收集的之后，您可选择此动作（通过其名称）并在此保存此查询。这样之后它将在计划任务中执行。（注意选中的高级搜索中的输出选择表单已存储，因此确保在那选择CSV输出！）</label>
			<label index="assign_to_groups.description">选择允许在任务中心激活动作的后台用户组。</label>
			<label index="t1_userprefix.description">为新用户名输入一个前缀，该前缀强制添加到新用户名前。</label>
			<label index="t1_allowed_groups.description">输入一个后台用户组，该组中用户能选择并执行一个动作。</label>
			<label index="t1_create_user_dir.description">如果选中，在创建用户的同时创建一个用户私人的主目录。</label>
			<label index="t1_create_user_dir.details">&lt;strong&gt;注意:&lt;/strong&gt; $TYPO3_CONF_VARS[&quot;BE&quot;][&quot;userHomePath&quot;] 必须按照$TYPO3_CONF_VARS[&quot;BE&quot;][&quot;lockRootPath&quot;] 配置并可写入！</label>
			<label index="t1_copy_of_user.description">插入一个当前的后台用户，该用户作为新建用户的模板。</label>
			<label index="t1_copy_of_user.details">所有值都复制给新用户，除了用户名，密码，名称和email。If the template user is a member of a group which is not defined among the &quot;Groups which may be assigned through the action&quot; that group is still set for the user and cannot be removed by the user carrying out the action.</label>
			<label index="t4_recordsToEdit.description">[FILL IN] sys_action-&gt;t4_recordsToEdit</label>
			<label index="t3_listPid.description">[FILL IN] sys_action-&gt;t3_listPid</label>
			<label index="t3_tables.description">[FILL IN] sys_action-&gt;t3_tables</label>
		</languageKey>
	</data>
	<orig_hash type="array">
		<languageKey index="ch" type="array">
			<label index=".description" type="integer">154099496</label>
			<label index=".details" type="integer">101422073</label>
			<label index="title.description" type="integer">235278962</label>
			<label index="description.description" type="integer">1063095</label>
			<label index="hidden.description" type="integer">229168195</label>
			<label index="hidden.details" type="integer">44953440</label>
			<label index="type.description" type="integer">245979443</label>
			<label index="assign_to_groups.description" type="integer">229842449</label>
			<label index="t1_userprefix.description" type="integer">100478470</label>
			<label index="t1_allowed_groups.description" type="integer">214180447</label>
			<label index="t1_create_user_dir.description" type="integer">85504709</label>
			<label index="t1_create_user_dir.details" type="integer">116051991</label>
			<label index="t1_copy_of_user.description" type="integer">122183518</label>
			<label index="t1_copy_of_user.details" type="integer">75966498</label>
			<label index="t4_recordsToEdit.description" type="integer">254072891</label>
			<label index="t3_listPid.description" type="integer">92767552</label>
			<label index="t3_tables.description" type="integer">184599860</label>
			<label index="type.details" type="integer">60868023</label>
		</languageKey>
	</orig_hash>
	<orig_text type="array">
		<languageKey index="ch" type="array">
			<label index=".description">An 'Action' is a configuration of a specific task which may be performed by assigned usergroups via the Task Center.</label>
			<label index=".details">Currently an Action may be configured to create additional backend usergroups without being and admin-user and by selecting from a limited set of options. Another option is to let an action initiate a SQL SELECT-query in the database and return the result as a CSV file.
Actions can be assigned to a Backend usergroup and they are activated by a single click in the Task Center.</label>
			<label index="title.description">Enter the title of the action. This is shown in the list of available actions in the Task Center.</label>
			<label index="description.description">Describe what the action does or allows to do.</label>
			<label index="hidden.description">Check this option if you wish to disable the availability of the action or non-admin users.</label>
			<label index="hidden.details">This option is a great way to disable an action during changes made to it because it still allows you as an 'Admin'-user to activate it for test purposes.</label>
			<label index="type.description">Select the action type.</label>
			<label index="assign_to_groups.description">Select the backend users groups allowed to activate the action in the Task Center.</label>
			<label index="t1_userprefix.description">Enter a prefix which is forcibly prepended to new usernames (eg. &quot;news_&quot;)</label>
			<label index="t1_allowed_groups.description">Enter the Backend user groups which the user performing the action is able to choose among (if any).</label>
			<label index="t1_create_user_dir.description">If checked, a private home-directory is also created during user creation. </label>
			<label index="t1_create_user_dir.details">&lt;strong&gt;Notice:&lt;/strong&gt; $TYPO3_CONF_VARS[&quot;BE&quot;][&quot;userHomePath&quot;] must be configured correctly along with $TYPO3_CONF_VARS[&quot;BE&quot;][&quot;lockRootPath&quot;] and writable!</label>
			<label index="t1_copy_of_user.description">Insert a current Backend user which will be used as a template for the new users created. </label>
			<label index="t1_copy_of_user.details">All values are copied to the new user, except username, password, name and email is of course overridden.
If the template user is a member of a group which is not defined among the &quot;Groups which may be assigned through the action&quot; that group is still set for the user and cannot be removed by the user carrying out the action.</label>
			<label index="t4_recordsToEdit.description">[FILL IN] sys_action-&gt;t4_recordsToEdit</label>
			<label index="t3_listPid.description">[FILL IN] sys_action-&gt;t3_listPid</label>
			<label index="t3_tables.description">[FILL IN] sys_action-&gt;t3_tables</label>
			<label index="type.details">&lt;strong&gt;&quot;Create Backend User&quot;&lt;/strong&gt; allows to create backend users with a limited set of options. This action type is meant for semi-administrators among your users which is in charge of daily user administration - still without being full fledged 'Admin'-users with 'a License to Kill everything'.
When you select this option, you get to enter a 'template' user, enter a prefix which the new users will automatically have and whether or not a user home-dir is created in the proces. Finally you can select a limited number of usergroups which the can be selected among.

&lt;strong&gt;&quot;SQL-query&quot;&lt;/strong&gt; allows to make a fixed SQL SELECT-query in the database returned as CSV lists. When you have created an action of this type, you need to go to the Tools&gt;DBint module and enter the Advanced Search feature. Here you can design your SQL-query. When you have designed it to select what you want correctly, you can select this action (by it's name) and save the query to the action there. From that point it will be effective from the Task Center. (Notice that the form of output selected in the Advanced Search function is also stored, so make sure to select CSV output there!)
</label>
		</languageKey>
	</orig_text>
</T3locallangExt>