snipe-it/resources/lang/en-ID/admin/statuslabels/message.php

33 lines
1.5 KiB
PHP
Raw Normal View History

2016-03-25 01:18:05 -07:00
<?php
return array(
2016-06-02 19:01:09 -07:00
'does_not_exist' => 'Status Label does not exist.',
'assoc_assets' => 'This Status Label is currently associated with at least one Asset and cannot be deleted. Please update your assets to no longer reference this status and try again. ',
2016-03-25 01:18:05 -07:00
'create' => array(
2016-06-02 19:01:09 -07:00
'error' => 'Status Label was not created, please try again.',
'success' => 'Status Label created successfully.'
2016-03-25 01:18:05 -07:00
),
'update' => array(
2016-06-02 19:01:09 -07:00
'error' => 'Status Label was not updated, please try again',
'success' => 'Status Label updated successfully.'
2016-03-25 01:18:05 -07:00
),
'delete' => array(
2016-06-02 19:01:09 -07:00
'confirm' => 'Are you sure you wish to delete this Status Label?',
'error' => 'There was an issue deleting the Status Label. Please try again.',
'success' => 'The Status Label was deleted successfully.'
2017-10-17 18:52:20 -07:00
),
'help' => array(
'undeployable' => 'These assets cannot be assigned to anyone.',
'deployable' => 'These assets can be checked out. Once they are assigned, they will assume a meta status of <i class="fa fa-circle text-blue"></i> <strong>Deployed</strong>.',
'archived' => 'These assets cannot be checked out, and will only show up in the Archived view. This is useful for retaining information about assets for budgeting/historic purposes but keeping them out of the day-to-day asset list.',
'pending' => 'These assets can not yet be assigned to anyone, often used for items that are out for repair, but are expected to return to circulation.',
),
2016-03-25 01:18:05 -07:00
);