Declaring Rule Inputs in child interface

A lot of child interfaces don't have variables(ri!) declared. Does not declaring ri! in child interface cause any performance or any such issues? If yes, then this should be made a part of best practice. 

  Discussion posts and replies are publicly visible

Parents
  • Yes it is a best practice to declare the rule inputs. There are many reasons to that.
    It will make easier to maintain
    Defining rule input allows you to test the user interface.
    Interface can be reused in many places and it will be easy for someone other than the developer who developed the interface to use it.
    If we do not define rule inputs the context of the interface limits to the parent interface most of the time as this will have a tight coupling due to the way we set and use variables in child and parent interfaces.

    So define your rule inputs that is a best practice.

    Regards
    Suresh
Reply
  • Yes it is a best practice to declare the rule inputs. There are many reasons to that.
    It will make easier to maintain
    Defining rule input allows you to test the user interface.
    Interface can be reused in many places and it will be easy for someone other than the developer who developed the interface to use it.
    If we do not define rule inputs the context of the interface limits to the parent interface most of the time as this will have a tight coupling due to the way we set and use variables in child and parent interfaces.

    So define your rule inputs that is a best practice.

    Regards
    Suresh
Children
No Data