PHD Help Desk 1.40 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News PHD Help Desk 1.40 (Default branch)
# 1  
Old 09-01-2008
PHD Help Desk 1.40 (Default branch)

ImagePHD Help Desk is software conceived for theregistry and follow-up ofhelp desks incidents. Registry of incidents allowsclassification in twolevels (type and subtype), the state of theincident, a description,ticket assignment and priority, historicalregistry, and an audit.Information can be reported in consultationformat, to give reportsor export the information for later processing ina database orspreadsheet.License: GNU General Public License (GPL)Changes:
The administration screens for areas, users,attributes, sectors, and operators administratoroptions were improved, adding filters andsplitting the data for best management. Anoperator configuration option was added forreceiving an email alert when a user loads asupport request. Parameters can be administrateddirectly from the software. It is possible toconfigure default values for the ticketattributes.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
Moose::Meta::TypeConstraint::Registry(3)		User Contributed Perl Documentation		  Moose::Meta::TypeConstraint::Registry(3)

NAME
Moose::Meta::TypeConstraint::Registry - registry for type constraints VERSION
version 2.0604 DESCRIPTION
This class is a registry that maps type constraint names to Moose::Meta::TypeConstraint objects. Currently, it is only used internally by Moose::Util::TypeConstraints, which creates a single global registry. INHERITANCE
"Moose::Meta::TypeConstraint::Registry" is a subclass of Class::MOP::Object. METHODS
Moose::Meta::TypeConstraint::Registry->new(%options) This creates a new registry object based on the provided %options: o parent_registry This is an optional Moose::Meta::TypeConstraint::Registry object. o type_constraints This is hash reference of type names to type objects. This is optional. Constraints can be added to the registry after it is created. $registry->get_parent_registry Returns the registry's parent registry, if it has one. $registry->has_parent_registry Returns true if the registry has a parent. $registry->set_parent_registry($registry) Sets the parent registry. $registry->get_type_constraint($type_name) This returns the Moose::Meta::TypeConstraint object from the registry for the given name, if one exists. $registry->has_type_constraint($type_name) Returns true if the registry has a type of the given name. $registry->add_type_constraint($type) Adds a new Moose::Meta::TypeConstraint object to the registry. $registry->find_type_constraint($type_name) This method looks in the current registry for the named type. If the type is not found, then this method will look in the registry's parent, if it has one. BUGS
See "BUGS" in Moose for details on reporting bugs. AUTHOR
Moose is maintained by the Moose Cabal, along with the help of many contributors. See "CABAL" in Moose and "CONTRIBUTORS" in Moose for details. COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Infinity Interactive, Inc.. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.16.2 2012-09-19 Moose::Meta::TypeConstraint::Registry(3)