[Nishit Shan]

in reply to: Maseter Port Out PIN #13926

Hello Andrey,

I have started working on Bulk edit, will let you know about the progress.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13924

Hello Andrey,

Thanks for #13923. I will check Bulk Edit task and get back to you if needed.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13921

Hello Andrey,

I have completed master port out pin entry for both admin and user side , you can test and know me after process.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13918

Hello Andrey,

Thanks for your input , i will change my current design accordingly.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13912

Hello Andrey,

Thanks for #13910. I have made the input fields work on the admin side for the edit profile section. Now, I am working on the script for the frontend profile settings page. I will update you once I complete the entry process on both the admin and frontend sides.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13909

Hello Andrey,

I am currently adding master port out pin for the customer on both admin and user site and activate and deactivate option. Letter i will ask to so me the process where pin will be required . Because i still have some confusion but i also don’t want to delay the task ,so i am currently doing what i got.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13907

Hello Andrey,

I have reviewed the newly added task description and noticed some changes that will impact the API and other parts of the code. I will need to review the affected areas in the codebase and then discuss it with my boss. This is a time-consuming process, so I will get back to you once I have completed the review.

• This reply was modified 3 weeks, 1 day ago by Nishit Shan.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13905

Hello Andrey,

Thanks for update , i will check and will start working. I will get back to you if needed.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13900

Hello Andrey,

I have started working on master port out pin and have added input field for both profile setting page and admin side edit user page, you can check.

While we have no update from admin side i will check bulk update task as you said and i will get back to you , if needed.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13896

Hello Andrey,

Yes, but why default PIN number universal for customers active numbers ? I am asking because i have to know what will be it’s behaviour once we created it and make it as active .For example will it be used for any type of filtering or other thing.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13894

Hello Andrey,

Currently i am checking all connected code with profile setting and edit user , so there can be no conflict between our code and previous code.

Should master pin out be unique ? Can you please give me an idea where this pin will be used , like do you have any page or API so i can just remind myself about that code.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13891

Hello Andrey,

All job inside this task page is not yet been completed “Master Port Out PIN and Bulk Edit Numbers Improvment” still have to do.

With your permission i am going to look into both of these task , i will let you know if there will be any questions or confusion.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13888

Hello Andrey,

I want to ask if there is any task listed which should i prioritise or should i go in flow ?

[Nishit Shan]

in reply to: Maseter Port Out PIN #13881

Hello Andrey,
Additionally, users cannot include “-” in the brand name, as the system automatically removes hyphens when searching the brand name in the database.

I’ve updated the brand name to “Matching NPA NXX (305.305 etc)” and added one number — (254) 254-0000 — under the “TEXAS”, “Matching NPA NXX (305.305 etc)”, and its original “New Number” brand. The number now appears in the product listings of all three brands.

[Nishit Shan]

in reply to: Maseter Port Out PIN #13879

Hello Andrey,

Thank you for your feedback.

I reviewed the issue and noticed that the brand not is not matching the expected NPA/NXX format (e.g., 305.305). This appears to be due to the brand name containing a “/” character. Since the system uses the brand name as a URL parameter, “/” is not allowed in the brand name.

I’m currently looking into resolving the issue by updating the brand name.

• This reply was modified 4 weeks, 1 day ago by Nishit Shan.

[Author]

Posts