mirror of
https://github.com/snipe/snipe-it.git
synced 2024-12-28 06:59:41 -08:00
46f5f21368
* Added “show fields in email” to custom fields * Added “show images in email” to settings * Added nicer HTML emails * Break notifications out into their own, instead of trying to mash them all together * Remove old notification for accessory checkout * Janky fix for #5076 - “The asset you have attempted to accept was not checked out to you” * Add method for image url for accessories * Added accessory checkout email blade * Make accessory email notification on checkout screen consistent with assets * Added native consumables notifications * Fixes for asset notification * Updated notification blades with correct-er fields * Updated notifications * License checkin notification - does not work yet Need to figure out whether the license seat is assigned to a person or an asset before we can pass the target * Added alternate “cc” email for admins * Only try to trigger notifications if the target is a user * Fix tests * Fixed consumable URL * Removed unused notification * Pass target type in params * Show slack status * Pass additional parameters There is a logic bug in this :( Will send to slack twice, since the admin CC and the user are both using the same notification. Fuckity fuck fuck fuck. * Pass a variable to the notification to supress the duplicate slack message * Slack is broken :( Trying to fix Will try a git bisect * Put preview back into checkout * Pulled old archaic mail * Removed debugging * Fixed wrong email title * Fixed slack endpoint not firing * Poobot, we hardly knew ye. * Removed old, manual mail from API * Typo :-/ * Code cleanup * Use defined formatted date in JSON * Use static properties for checkin/checkout notifiers for cleaner code * Removed debugging * Use date formatter * Fixed target_type * Fixed language in consumable email
33 lines
2 KiB
PHP
33 lines
2 KiB
PHP
<?php
|
|
|
|
return array(
|
|
'custom_fields' => 'Custom Fields',
|
|
'field' => 'Field',
|
|
'about_fieldsets_title' => 'About Fieldsets',
|
|
'about_fieldsets_text' => 'Fieldsets allow you to create groups of custom fields that are frequently re-used used for specific asset model types.',
|
|
'custom_format' => 'Custom regex format...',
|
|
'encrypt_field' => 'Encrypt the value of this field in the database',
|
|
'encrypt_field_help' => 'WARNING: Encrypting a field makes it unsearchable.',
|
|
'encrypted' => 'Encrypted',
|
|
'fieldset' => 'Fieldset',
|
|
'qty_fields' => 'Qty Fields',
|
|
'fieldsets' => 'Fieldsets',
|
|
'fieldset_name' => 'Fieldset Name',
|
|
'field_name' => 'Field Name',
|
|
'field_values' => 'Field Values',
|
|
'field_values_help' => 'Add selectable options, one per line. Blank lines other than the first line will be ignored.',
|
|
'field_element' => 'Form Element',
|
|
'field_element_short' => 'Element',
|
|
'field_format' => 'Format',
|
|
'field_custom_format' => 'Custom Regex Format',
|
|
'field_custom_format_help' => 'This field allows you to use a regex expression for validation. It should start with "regex:" - for example, to validate that a custom field value contains a valid IMEI (15 numeric digits), you would use <code>regex:/^[0-9]{15}$/</code>.',
|
|
'required' => 'Required',
|
|
'req' => 'Req.',
|
|
'used_by_models' => 'Used By Models',
|
|
'order' => 'Order',
|
|
'create_fieldset' => 'New Fieldset',
|
|
'create_field' => 'New Custom Field',
|
|
'value_encrypted' => 'The value of this field is encrypted in the database. Only admin users will be able to view the decrypted value',
|
|
'show_in_email' => 'Include the value of this field in checkout emails sent to the user? Encrypted fields cannot be included in emails.',
|
|
);
|